[Home] [Help]
PACKAGE: APPS.OTA_CTU_BUS
Source
1 Package ota_ctu_bus as
2 /* $Header: otcturhi.pkh 120.0 2005/05/29 07:10:39 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_category_usage_id
15 -- already exists.
16 --
17 -- In Arguments:
18 -- p_category_usage_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_category_usage_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_category_usage_id
48 -- already exists.
49 --
50 -- In Arguments:
51 -- p_category_usage_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_category_usage_id in number
67 ) RETURN varchar2;
68 --
69 --
70 -- ----------------------------------------------------------------------------
71 -- |---------------------------< insert_validate >----------------------------|
72 -- ----------------------------------------------------------------------------
73 -- {Start of comments}
74 --
75 -- Description:
76 -- This procedure controls the execution of all insert business rules
77 -- validation.
78 --
79 -- Prerequisites:
80 -- This private procedure is called from ins procedure.
81 --
82 -- In Parameters:
83 -- A Pl/Sql record structure.
84 --
85 -- Post Success:
86 -- Processing continues.
87 --
88 -- Post Failure:
89 -- If a business rules fails the error will not be handled by this procedure
90 -- unless explicity coded.
91 --
92 -- Developer Implementation Notes:
93 -- For insert, your business rules should be executed from this procedure
94 -- and should ideally (unless really necessary) just be straight procedure
95 -- or function calls. Try and avoid using conditional branching logic.
96 --
97 -- Access Status:
98 -- Internal Row Handler Use Only.
99 --
100 -- {End of comments}
101 -- ----------------------------------------------------------------------------
102 Procedure insert_validate
103 (p_effective_date in date
104 ,p_rec in ota_ctu_shd.g_rec_type
105 );
106 --
107 -- ----------------------------------------------------------------------------
108 -- |---------------------------< update_validate >----------------------------|
109 -- ----------------------------------------------------------------------------
110 -- {Start Of Comments}
111 --
112 -- Description:
113 -- This procedure controls the execution of all update business rules
114 -- validation.
115 --
116 -- Prerequisites:
117 -- This private procedure is called from upd procedure.
118 --
119 -- In Parameters:
120 -- A Pl/Sql record structure.
121 --
122 -- Post Success:
123 -- Processing continues.
124 --
125 -- Post Failure:
126 -- If a business rules fails the error will not be handled by this procedure
127 -- unless explicity coded.
128 --
129 -- Access Status:
130 -- Internal Row Handler Use Only.
131 --
132 -- {End Of Comments}
133 -- ----------------------------------------------------------------------------
134 Procedure update_validate
135 (p_effective_date in date
136 ,p_rec in ota_ctu_shd.g_rec_type
137 );
138 --
139 -- ----------------------------------------------------------------------------
140 -- |---------------------------< delete_validate >----------------------------|
141 -- ----------------------------------------------------------------------------
142 -- {Start Of Comments}
143 --
144 -- Description:
145 -- This procedure controls the execution of all delete business rules
146 -- validation.
147 --
148 -- Prerequisites:
149 -- This private procedure is called from del procedure.
150 --
151 -- In Parameters:
152 -- A Pl/Sql record structure.
153 --
154 -- Post Success:
155 -- Processing continues.
156 --
157 -- Post Failure:
158 -- If a business rules fails the error will not be handled by this procedure
159 -- unless explicity coded.
160 --
161 -- Developer Implementation Notes:
162 -- For delete, your business rules should be executed from this procedure
163 -- and should ideally (unless really necessary) just be straight procedure
164 -- or function calls. Try and avoid using conditional branching logic.
165 --
166 -- Access Status:
167 -- Internal Row Handler Use Only.
168 --
169 -- {End Of Comments}
170 -- ----------------------------------------------------------------------------
171 Procedure delete_validate
172 (p_rec in ota_ctu_shd.g_rec_type
173 );
174 -- ----------------------------------------------------------------------------
175 -- |---------------------< Chk_valid_parent_category >------------------------|
176 -- ----------------------------------------------------------------------------
177 -- {Start Of Comments}
178 --
179 -- Description:
180 --
181 -- This business process validates the parent category while creating or updating a Category.
182 --
183 -- {End Of Comments}
184 --
185 Procedure Chk_valid_parent_category
186 (p_parent_cat_usage_id in number
187 ,p_category_usage_id in number
188 );
189 --
190 -- ----------------------------------------------------------------------------
191 -- |------------------------< Chk_child_category >----------------------------|
192 -- ----------------------------------------------------------------------------
193 -- {Start of comments}
194 --
195 -- Description:
196 --
197 --
198 -- Pre-requisites
199 --
200 --
201 -- Post Success:
202 --
203 --
204 -- Post Failure:
205 --
206 --
207 -- Access Status:
208 -- Internal Development use only.
209 --
210 -- {End of comments}
211 -- ----------------------------------------------------------------------------
212 Procedure Chk_child_category
213 (p_category_usage_id in number
214 );
215 --
216 -- ----------------------------------------------------------------------------
217 -- |------------------------< Chk_act_association >---------------------------|
218 -- ----------------------------------------------------------------------------
219 -- {Start of comments}
220 --
221 -- Description:
222 --
223 --
224 -- Pre-requisites
225 --
226 --
227 -- Post Success:
228 --
229 --
230 -- Post Failure:
231 --
232 --
233 -- Access Status:
234 -- Internal Development use only.
235 --
236 -- {End of comments}
237 -- ----------------------------------------------------------------------------
238 Procedure Chk_act_association
239 (p_category_usage_id in number
240 );
241 --
242 -- ----------------------------------------------------------------------------
243 -- |----------------------< Chk_offering_association >------------------------|
244 -- ----------------------------------------------------------------------------
245 -- {Start of comments}
246 --
247 -- Description:
248 --
249 --
250 -- Pre-requisites
251 --
252 --
253 -- Post Success:
254 --
255 --
256 -- Post Failure:
257 --
258 --
259 -- Access Status:
260 -- Internal Development use only.
261 --
262 -- {End of comments}
263 -- ----------------------------------------------------------------------------
264 Procedure Chk_offering_association
265 (p_category_usage_id in number
266 );
267 --
268 -- ----------------------------------------------------------------------------
269 -- |-------------------------< Chk_online_flag >------------------------------|
270 -- ----------------------------------------------------------------------------
271 -- {Start of comments}
272 --
273 -- Description:
274 --
275 --
276 -- Pre-requisites
277 --
278 --
279 -- Post Success:
280 --
281 --
282 -- Post Failure:
283 --
284 --
285 -- Access Status:
286 -- Internal Development use only.
287 --
288 -- {End of comments}
289 -- ----------------------------------------------------------------------------
290 Procedure Chk_online_flag
291 (p_online_flag in varchar2
292 ,p_type in varchar2
293 );
294 --
295 -- ----------------------------------------------------------------------------
296 -- |----------------------< Chk_synchronous_flag >------------------------|
297 -- ----------------------------------------------------------------------------
298 -- {Start of comments}
299 --
300 -- Description:
301 --
302 --
303 -- Pre-requisites
304 --
305 --
306 -- Post Success:
307 --
308 --
309 -- Post Failure:
310 --
311 --
312 -- Access Status:
313 -- Internal Development use only.
314 --
315 -- {End of comments}
316 -- ----------------------------------------------------------------------------
317 Procedure Chk_synchronous_flag
318 (p_synchronous_flag in varchar2
319 ,p_type in varchar2
320 );
321 --
322 -- ----------------------------------------------------------------------------
323 -- |-------------------------< Chk_start_end_dates >--------------------------|
324 -- ----------------------------------------------------------------------------
325 -- {Start of comments}
326 --
327 -- Description:
328 --
329 --
330 -- Pre-requisites
331 --
332 --
333 -- Post Success:
334 --
335 --
336 -- Post Failure:
337 --
338 --
339 -- Access Status:
340 -- Internal Development use only.
341 --
342 -- {End of comments}
343 -- ----------------------------------------------------------------------------
344 Procedure Chk_start_end_dates
345 (p_start_date in date
346 ,p_end_date in date
347 );
348 --
349 -- ----------------------------------------------------------------------------
350 -- |------------------------< Chk_lp_association >---------------------------|
351 -- ----------------------------------------------------------------------------
352 -- {Start of comments}
353 --
354 -- Description:
355 --
356 --
357 -- Pre-requisites
358 --
359 --
360 -- Post Success:
361 --
362 --
363 -- Post Failure:
364 --
365 --
366 -- Access Status:
367 -- Internal Development use only.
368 --
369 -- {End of comments}
370 -- ----------------------------------------------------------------------------
371 Procedure Chk_lp_association
372 (p_category_usage_id in number
373 );
374 --
375 -- ----------------------------------------------------------------------------
376 -- |-----------------------< Chk_act_def_for_org_tp>--------------------------|
377 -- ----------------------------------------------------------------------------
378 -- {Start of comments}
379 --
380 -- Description:
381 --
382 --
383 -- Pre-requisites
384 --
385 --
386 -- Post Success:
387 --
388 --
389 -- Post Failure:
390 --
391 --
392 -- Access Status:
393 -- Internal Development use only.
394 --
395 -- {End of comments}
396 -- ----------------------------------------------------------------------------
397 Procedure Chk_act_def_for_org_tp
398 (p_category_usage_id in number
399 );
400 --
401 end ota_ctu_bus;