1 Package ota_adt_bus as
2 /* $Header: otadtrhi.pkh 120.1 2005/07/11 07:32:22 pgupta 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_id
15 -- already exists.
16 --
17 -- In Arguments:
18 -- p_activity_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_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_id
48 -- already exists.
49 --
50 -- In Arguments:
51 -- p_activity_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_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_adt_shd.g_rec_type
106 ,p_activity_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_adt_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_adt_shd.g_rec_type
175 );
176 --
177 -- ----------------------------------------------------------------------------
178 -- |---------------------------< set_translation_globals >------------------------|
179 -- ----------------------------------------------------------------------------
180 -- {Start Of Comments}
181 --
182 -- Description:
183 -- This procedure initialize the global variable Business_global_id.
184 -- This global variable is required to check the uniqueness of a name.
185 --
186 -- Prerequisites:
187 -- This procedure is called just before Validate_translation.
188 --
189 -- In Parameters:
190 -- Business_group_id
191 --
192 -- Post Success:
193 -- Processing continues.
194 --
195 -- Post Failure:
196 -- If a business rules fails the error will not be handled by this procedure
197 -- and returns the error status
198 --
199 -- Developer Implementation Notes:
200 --
201 -- Access Status:
202 -- called from Translation trigger of a form which support MLS.
203 --
204 -- {End Of Comments}
205 -- ----------------------------------------------------------------------------
206 PROCEDURE set_translation_globals
207 (p_business_group_id in number
208 ) ;
209 --
210
211 -- ----------------------------------------------------------------------------
212 -- |---------------------------< Check_Unique_name >------------------------|
213 -- ----------------------------------------------------------------------------
214 -- {Start Of Comments}
215 --
216 -- Description:
217 -- This procedure performs the validation for the uniqueness of a name.
218 --
219 -- Prerequisites:
220 -- This procedure is called from from Validate_translation.
221 --
222 -- In Parameters:
223 -- Business_group_id, Name, Activity_id, Language
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 -- and returns the error status
231 --
232 -- Developer Implementation Notes:
233 --
234 -- Access Status:
235 -- MLS Widget Only.
236 --
237 -- {End Of Comments}
238 -- ----------------------------------------------------------------------------
239 procedure CHECK_UNIQUE_NAME (
240 P_BUSINESS_GROUP_ID in number,
241 P_NAME in varchar2,
242 P_LANGUAGE in varchar2,
243 P_ACTIVITY_ID in number
244 ) ;
245 --
246 -- ----------------------------------------------------------------------------
247 -- |---------------------------< validate_translation >------------------------|
248 -- ----------------------------------------------------------------------------
249 -- {Start Of Comments}
250 --
251 -- Description:
252 -- This procedure fetch the business group id for the passed in activity_id
253 -- and then calls check_unique_name to validate the uniqueness of a name.
254 --
255 -- Prerequisites:
256 -- This procedure is called from from Insert_validate and Update_validate.
257 --
258 -- In Parameters:
259 -- Business_group_id, Name, Activity_id, Language as Record type
260 -- Since when this is called from insert_validate the rec_type contains NULL for
261 -- activity_id additionally it receives Activity_id as seperate parameter
262 --
263 -- Post Success:
264 -- Processing continues.
265 --
266 -- Post Failure:
267 -- If a business rules fails the error will not be handled by this procedure
268 --
269 -- Developer Implementation Notes:
270 --
271 -- Access Status:
272 -- MLS Widget Only.
273 --
274 -- {End Of Comments}
275 -- ----------------------------------------------------------------------------
276 Procedure validate_translation
277 (activity_id in number
278 ,language in varchar2
279 ,name in varchar2
280 ,description in varchar2
281 ,p_business_group_id in number default null
282 );
283 --
284 end ota_adt_bus;
[Home] [Help]