1 Package ota_avt_bus as
2 /* $Header: otavtrhi.pkh 120.0 2005/05/29 07:02:23 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_activity_version_id
15 -- already exists.
16 --
17 -- In Arguments:
18 -- p_activity_version_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_activity_version_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_activity_version_id
48 -- already exists.
49 --
50 -- In Arguments:
51 -- p_activity_version_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_activity_version_id in number
67 ,p_language in varchar2
68 ) RETURN varchar2;
69 --
70 --
71 -- ----------------------------------------------------------------------------
72 -- |---------------------------< insert_validate >----------------------------|
73 -- ----------------------------------------------------------------------------
74 -- {Start of comments}
75 --
76 -- Description:
77 -- This procedure controls the execution of all insert business rules
78 -- validation.
79 --
80 -- Prerequisites:
81 -- This private procedure is called from ins procedure.
82 --
83 -- In Parameters:
84 -- A Pl/Sql record structure.
85 --
86 -- Post Success:
87 -- Processing continues.
88 --
89 -- Post Failure:
90 -- If a business rules fails the error will not be handled by this procedure
91 -- unless explicity coded.
92 --
93 -- Developer Implementation Notes:
94 -- For insert, your business rules should be executed from this procedure
95 -- and should ideally (unless really necessary) just be straight procedure
96 -- or function calls. Try and avoid using conditional branching logic.
97 --
98 -- Access Status:
99 -- Internal Row Handler Use Only.
100 --
101 -- {End of comments}
102 -- ----------------------------------------------------------------------------
103 Procedure insert_validate
104 (p_effective_date in date
105 ,p_rec in ota_avt_shd.g_rec_type
106 ,p_activity_version_id in number
107 );
108 --
109 -- ----------------------------------------------------------------------------
110 -- |---------------------------< update_validate >----------------------------|
111 -- ----------------------------------------------------------------------------
112 -- {Start Of Comments}
113 --
114 -- Description:
115 -- This procedure controls the execution of all update business rules
116 -- validation.
117 --
118 -- Prerequisites:
119 -- This private procedure is called from upd procedure.
120 --
121 -- In Parameters:
122 -- A Pl/Sql record structure.
123 --
124 -- Post Success:
125 -- Processing continues.
126 --
127 -- Post Failure:
128 -- If a business rules fails the error will not be handled by this procedure
129 -- unless explicity coded.
130 --
131 -- Access Status:
132 -- Internal Row Handler Use Only.
133 --
134 -- {End Of Comments}
135 -- ----------------------------------------------------------------------------
136 Procedure update_validate
137 (p_effective_date in date
138 ,p_rec in ota_avt_shd.g_rec_type
139 );
140 --
141 -- ----------------------------------------------------------------------------
142 -- |---------------------------< delete_validate >----------------------------|
143 -- ----------------------------------------------------------------------------
144 -- {Start Of Comments}
145 --
146 -- Description:
147 -- This procedure controls the execution of all delete business rules
148 -- validation.
149 --
150 -- Prerequisites:
151 -- This private procedure is called from del procedure.
152 --
153 -- In Parameters:
154 -- A Pl/Sql record structure.
155 --
156 -- Post Success:
157 -- Processing continues.
158 --
159 -- Post Failure:
160 -- If a business rules fails the error will not be handled by this procedure
161 -- unless explicity coded.
162 --
163 -- Developer Implementation Notes:
164 -- For delete, your business rules should be executed from this procedure
165 -- and should ideally (unless really necessary) just be straight procedure
166 -- or function calls. Try and avoid using conditional branching logic.
167 --
168 -- Access Status:
169 -- Internal Row Handler Use Only.
170 --
171 -- {End Of Comments}
172 -- ----------------------------------------------------------------------------
173 Procedure delete_validate
174 (p_rec in ota_avt_shd.g_rec_type
175 );
176 --
177 --
178 -- ----------------------------------------------------------------------------
179 -- |-----------------------< set_translation_globals >------------------------|
180 -- ----------------------------------------------------------------------------
181 -- {Start Of Comments}
182 --
183 -- Description:
184 -- This procedure sets the value required to perform the validation for the
185 -- MLS widget.
186 --
187 -- Prerequisites:
188 -- This procedure is called from from Translations trigger of MLS block.
189 --
190 -- In Parameters:
191 -- Business_Group_id, Activity_id
192 --
193 -- Post Success:
194 -- Processing continues.
195 --
196 -- Post Failure:
197 -- If a business rules fails the error will not be handled by this procedure
198 --
199 -- Developer Implementation Notes:
200 --
201 -- Access Status:
202 -- MLS block Translations trigger.
203 PROCEDURE set_translation_globals
204 (p_business_group_id in number
205 ,p_activity_id in number
206 ) ;
207 -- ----------------------------------------------------------------------------
208 -- |---------------------------< validate_translation >------------------------|
209 -- ----------------------------------------------------------------------------
210 -- {Start Of Comments}
211 --
212 -- Description:
213 -- This procedure performs the validation for the MLS widget.
214 --
215 -- Prerequisites:
216 -- This procedure is called from from the MLS widget.
217 --
218 -- In Parameters:
219 --
220 -- Post Success:
221 -- Processing continues.
222 --
223 -- Post Failure:
224 -- If a business rules fails the error will not be handled by this procedure
225 --
226 -- Developer Implementation Notes:
227 --
228 -- Access Status:
229 -- MLS Widget Only.
230 --
231 -- {End Of Comments}
232 -- ----------------------------------------------------------------------------
233 Procedure validate_translation
234 (p_activity_version_id in number
235 ,p_language in varchar2
236 ,p_version_name in varchar2
237 ,p_description in varchar2
238 ,p_intended_audience in varchar2
239 ,p_objectives in varchar2
240 ,p_keywords in varchar2
241 ,p_business_group_id in number default null
242 ,p_activity_id in number default null
243 );
244 --
245 -- ----------------------------------------------------------------------------
246 -- |--------------------------< check_unique_version_name >---------------------------|
247 -- ----------------------------------------------------------------------------
248 -- {Start Of Comments}
249 --
250 -- Description:
251 -- This procedure performs the validation for the uniqueness of a name.
252 --
253 -- Prerequisites:
254 -- This procedure is called from from Validate_translation.
255 --
256 -- In Parameters:
257 -- Business_group_id, Name, Activity_id, Language
258 --
259 -- Post Success:
260 -- Processing continues.
261 --
262 -- Post Failure:
263 -- If a business rules fails the error will not be handled by this procedure
264 -- and returns the error status
265 --
266 -- Developer Implementation Notes:
267 --
268 -- Access Status:
269 -- MLS Widget Only.
270 --
271 -- {End Of Comments}
272 Procedure check_unique_version_name
273 (
274 p_business_group_id in number default null
275 ,p_activity_id in number default null
276 ,p_version_name in varchar2
277 ,p_activity_version_id in number
278 ,p_language in varchar2
279 ) ;
280 --
281 end ota_avt_bus;
[Home] [Help]