1 Package ota_cci_bus as
2 /* $Header: otccirhi.pkh 120.1 2005/07/21 15:03 estreacy 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_category_usage_id
15 -- p_certification_id
16 -- already exists.
17 --
18 -- In Arguments:
19 -- p_category_usage_id
20 -- p_certification_id
21 --
22 --
23 -- Post Success:
24 -- The security_group_id will be set in CLIENT_INFO.
25 --
26 -- Post Failure:
27 -- An error is raised if the value does not exist.
28 --
29 -- Access Status:
30 -- Internal Development Use Only.
31 --
32 -- {End Of Comments}
33 -- ---------------------------------------------------------------------------
34 procedure set_security_group_id
35 (p_category_usage_id in number
36 ,p_certification_id in number
37 ,p_associated_column1 in varchar2 default null
38 ,p_associated_column2 in varchar2 default null
39 );
40 --
41 --
42 -- ---------------------------------------------------------------------------
43 -- |---------------------< return_legislation_code >-------------------------|
44 -- ---------------------------------------------------------------------------
45 -- {Start Of Comments}
46 --
47 -- Description:
48 -- Return the legislation code for a specific primary key value
49 --
50 -- Prerequisites:
51 -- The primary key identified by p_category_usage_id
52 -- p_certification_id
53 -- already exists.
54 --
55 -- In Arguments:
56 -- p_category_usage_id
57 -- p_certification_id
58 --
59 --
60 -- Post Success:
61 -- The business group's legislation code will be returned.
62 --
63 -- Post Failure:
64 -- An error is raised if the value does not exist.
65 --
66 -- Access Status:
67 -- Internal Development Use Only.
68 --
69 -- {End Of Comments}
70 -- ---------------------------------------------------------------------------
71 FUNCTION return_legislation_code
72 (p_category_usage_id in number
73 ,p_certification_id in number
74 ) RETURN varchar2;
75 --
76 --
77 -- ----------------------------------------------------------------------------
78 -- |---------------------------< insert_validate >----------------------------|
79 -- ----------------------------------------------------------------------------
80 -- {Start of comments}
81 --
82 -- Description:
83 -- This procedure controls the execution of all insert business rules
84 -- validation.
85 --
86 -- Prerequisites:
87 -- This private procedure is called from ins procedure.
88 --
89 -- In Parameters:
90 -- A Pl/Sql record structure.
91 --
92 -- Post Success:
93 -- Processing continues.
94 --
95 -- Post Failure:
96 -- If a business rules fails the error will not be handled by this procedure
97 -- unless explicity coded.
98 --
99 -- Developer Implementation Notes:
100 -- For insert, your business rules should be executed from this procedure
101 -- and should ideally (unless really necessary) just be straight procedure
102 -- or function calls. Try and avoid using conditional branching logic.
103 --
104 -- Access Status:
105 -- Internal Row Handler Use Only.
106 --
107 -- {End of comments}
108 -- ----------------------------------------------------------------------------
109 Procedure insert_validate
110 (p_effective_date in date
111 ,p_rec in ota_cci_shd.g_rec_type
112 ,p_certification_id in number
113 ,p_category_usage_id in number
114 );
115 --
116 -- ----------------------------------------------------------------------------
117 -- |---------------------------< update_validate >----------------------------|
118 -- ----------------------------------------------------------------------------
119 -- {Start Of Comments}
120 --
121 -- Description:
122 -- This procedure controls the execution of all update business rules
123 -- validation.
124 --
125 -- Prerequisites:
126 -- This private procedure is called from upd procedure.
127 --
128 -- In Parameters:
129 -- A Pl/Sql record structure.
130 --
131 -- Post Success:
132 -- Processing continues.
133 --
134 -- Post Failure:
135 -- If a business rules fails the error will not be handled by this procedure
136 -- unless explicity coded.
137 --
138 -- Access Status:
139 -- Internal Row Handler Use Only.
140 --
141 -- {End Of Comments}
142 -- ----------------------------------------------------------------------------
143 Procedure update_validate
144 (p_effective_date in date
145 ,p_rec in ota_cci_shd.g_rec_type
146 );
147 --
148 -- ----------------------------------------------------------------------------
149 -- |---------------------------< delete_validate >----------------------------|
150 -- ----------------------------------------------------------------------------
151 -- {Start Of Comments}
152 --
153 -- Description:
154 -- This procedure controls the execution of all delete business rules
155 -- validation.
156 --
157 -- Prerequisites:
158 -- This private procedure is called from del procedure.
159 --
160 -- In Parameters:
161 -- A Pl/Sql record structure.
162 --
163 -- Post Success:
164 -- Processing continues.
165 --
166 -- Post Failure:
167 -- If a business rules fails the error will not be handled by this procedure
168 -- unless explicity coded.
169 --
170 -- Developer Implementation Notes:
171 -- For delete, your business rules should be executed from this procedure
172 -- and should ideally (unless really necessary) just be straight procedure
173 -- or function calls. Try and avoid using conditional branching logic.
174 --
175 -- Access Status:
176 -- Internal Row Handler Use Only.
177 --
178 -- {End Of Comments}
179 -- ----------------------------------------------------------------------------
180 Procedure delete_validate
181 (p_rec in ota_cci_shd.g_rec_type
182 );
183 --
184 -- ----------------------------------------------------------------------------
185 -- |---------------------------< check_if_primary_category >----------------------------|
186 -- ----------------------------------------------------------------------------
187 -- {Start Of Comments}
188 --
189 -- Description:
190 -- This procedure Checks if the given Category is Primary for the
191 -- certification.
192 --
193 -- Prerequisites:
194 -- This private procedure is called from insertValidate and UpdateValidate
195 --
196 -- In Parameters:
197 -- certification_id and Category_usage_id
198 --
199 -- Post Success:
200 -- Processing continues.
201 --
202 -- Post Failure:
203 -- If a business rules fails the error will not be handled by this procedure
204 -- unless explicity coded.
205 --
206 -- Developer Implementation Notes:
207 --
208 --
209 -- Access Status:
210 -- Internal Row Handler Use Only.
211 --
212 -- {End Of Comments}
213 -- ----------------------------------------------------------------------------
214 Procedure check_if_primary_category
215 (
216 p_certification_id in number
217 ,p_category_usage_id in number
218 );
219
220 -- ----------------------------------------------------------------------------
221 -- |---------------------------< check_multiple_primary_ctgr >----------------------------|
222 -- ----------------------------------------------------------------------------
223 -- {Start Of Comments}
224 --
225 -- Description:
226 -- This procedure checks if there are multiple Primary Categories.
227 -- validation.
228 --
229 -- Prerequisites:
230 -- This private procedure is called from insertValidate and UpdateValidate
231 --
232 -- In Parameters:
233 -- certification_id
234 --
235 -- Post Success:
236 -- Processing continues.
237 --
238 -- Post Failure:
239 -- If a business rules fails the error will not be handled by this procedure
240 -- unless explicity coded.
241 --
242 -- Developer Implementation Notes:
243 --
244 --
245 -- Access Status:
246 -- Internal Row Handler Use Only.
247 --
248 -- {End Of Comments}
249 -- ----------------------------------------------------------------------------
250 Procedure check_multiple_primary_ctgr
251 (
252 p_certification_id in number
253 );
254
255 -- ----------------------------------------------------------------------------
256 -- |---------------------------< check_start_end_dates >----------------------------|
257 -- ----------------------------------------------------------------------------
258 -- {Start Of Comments}
259 --
260 -- Description:
261 -- This procedure checks the sStart and End Dates for the inclusion.
262 --
263 -- Prerequisites:
264 -- This private procedure is called from insert_validate and update_validate.
265 --
266 -- In Parameters:
267 -- StartDate and EndDate for the Inclusion.
268 --
269 -- Post Success:
270 -- Processing continues.
271 --
272 -- Post Failure:
273 -- If a business rules fails the error will not be handled by this procedure
274 -- unless explicity coded.
275 --
276 -- Developer Implementation Notes:
277 --
278 --
279 -- Access Status:
280 -- Internal Row Handler Use Only.
281 --
282 -- {End Of Comments}
283 -- ----------------------------------------------------------------------------
284 Procedure check_start_end_dates
285 (
286 p_start_date in date
287 ,p_end_date in date
288 );
289
290 -- ----------------------------------------------------------------------------
291 -- |---------------------------< check_unique_key >----------------------------|
292 -- ----------------------------------------------------------------------------
293 -- {Start Of Comments}
294 --
295 -- Description:
296 -- This procedure checks whether the Category has already been attached to
297 -- the certification
298 --
299 -- Prerequisites:
300 -- This private procedure is called from insert_validate and update_validate.
301 --
302 -- In Parameters:
303 -- certification_id and Category_usage_id
304 --
305 -- Post Success:
306 -- Processing continues.
307 --
308 -- Post Failure:
309 -- If a business rules fails the error will not be handled by this procedure
310 -- unless explicity coded.
311 --
312 -- Developer Implementation Notes:
313 --
314 --
315 -- Access Status:
316 -- Internal Row Handler Use Only.
317 --
318 -- {End Of Comments}
319 -- ----------------------------------------------------------------------------
320 Procedure check_unique_key
321 (
322 p_certification_id in number
323 ,p_category_usage_id in number
324 );
325
326 -- ----------------------------------------------------------------------------
327 -- |---------------------------< check_category_dates >----------------------------|
328 -- ----------------------------------------------------------------------------
329 -- {Start Of Comments}
330 --
331 -- Description:
332 -- This procedure checks whether the start and end date are within the
333 -- category dates.
334 --
335 -- Prerequisites:
336 -- This private procedure is called from insert_validate and update_validate.
337 --
338 -- In Parameters:
339 -- p_category_usage_id - Category Usage Id
340 -- p_start_date - Start Date Active for the Inclusion
341 -- p_end_date - End Date Active for the Inclusion
342 --
343 -- Post Success:
344 -- Processing continues.
345 --
346 -- Post Failure:
347 -- If a business rules fails the error will not be handled by this procedure
348 -- unless explicity coded.
349 --
350 -- Developer Implementation Notes:
351 --
352 --
353 -- Access Status:
354 -- Internal Row Handler Use Only.
355 --
356 -- {End Of Comments}
357 -- ----------------------------------------------------------------------------
358 Procedure check_category_dates
359 (
360 p_category_usage_id in number
361 ,p_start_date in date
362 ,p_end_date in date
363 );
364 --
365 --
366 end ota_cci_bus;
[Home] [Help]