1 Package ota_ent_bus AUTHID CURRENT_USER as
2 /* $Header: otentrhi.pkh 120.0 2005/05/29 07:13:32 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_event_id
15 -- already exists.
16 --
17 -- In Arguments:
18 -- p_event_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_event_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_event_id
48 -- already exists.
49 --
50 -- In Arguments:
51 -- p_event_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_event_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_ent_shd.g_rec_type
106 ,p_event_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_ent_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_ent_shd.g_rec_type
175 );
176 --
177 -- ----------------------------------------------------------------------------
178 -- |-----------------------< set_translation_globals >------------------------|
179 -- ----------------------------------------------------------------------------
180 -- {Start Of Comments}
181 --
182 -- Description:
183 -- This procedure stores values required by validate_translations.
184 --
185 -- Prerequisites:
186 -- This procedure is called from from the MLS widget enabled forms.
187 --
188 -- In Parameters:
189 --
190 -- Post Success:
191 -- Processing continues.
192 --
193 -- Post Failure:
194 -- If a business rules fails the error will not be handled by this procedure
195 --
196 -- Developer Implementation Notes:
197 --
198 -- Access Status:
199 -- MLS Widget enabled forms only just before calling validate_translation.
200 --
201 -- {End Of Comments}
202 -- ----------------------------------------------------------------------------
203 PROCEDURE set_translation_globals
204 (p_business_group_id in number
205 ,p_parent_event_id in number default null
206 );
207 --
208 --
209 -- ----------------------------------------------------------------------------
210 -- |---------------------------< validate_translation >-----------------------|
211 -- ----------------------------------------------------------------------------
212 -- {Start Of Comments}
213 --
214 -- Description:
215 -- This procedure performs the validation for the MLS widget.
216 --
217 -- Prerequisites:
218 -- This procedure is called from from the MLS widget.
219 --
220 -- In Parameters:
221 --
222 -- Post Success:
223 -- Processing continues.
224 --
225 -- Post Failure:
226 -- If a business rules fails the error will not be handled by this procedure
227 --
228 -- Developer Implementation Notes:
229 --
230 -- Access Status:
231 -- MLS Widget Only.
232 --
233 -- {End Of Comments}
234 -- ----------------------------------------------------------------------------
235 Procedure validate_translation
236 (p_event_id in number
237 ,p_language in varchar2
238 ,p_title in varchar2
239 ,p_business_group_id in number default null
240 ,p_parent_event_id in number default null
241 );
242 --
243 -- ----------------------------------------------------------------------------
244 -- |----------------------< CHECK_TITLE_IS_UNIQUE >---------------------------|
245 -- ----------------------------------------------------------------------------
246 --
247 -- Validates the uniqueness of the event title (ignoring case).
248 --
249 procedure CHECK_TITLE_IS_UNIQUE (
250 P_TITLE in varchar2,
251 P_BUSINESS_GROUP_ID in number,
252 P_PARENT_EVENT_ID in number,
253 P_EVENT_ID in number default null,
254 P_LANGUAGE in varchar2
255 );
256 --
257 -- ----------------------------------------------------------------------------
258 -- |------------------------< UNIQUE_EVENT_TITLE >----------------------------|
259 -- ----------------------------------------------------------------------------
260 --
261 -- Returns TRUE if the event has a title which is unique within its
262 -- business group. If the event id is not null, then the check avoids
263 -- comparing the title against itself. Titles are compared regardless
264 -- of case.
265 --
266 function UNIQUE_EVENT_TITLE (
267 P_TITLE in varchar2,
268 P_BUSINESS_GROUP_ID in number,
269 P_PARENT_EVENT_ID in number,
270 P_EVENT_ID in number default null,
271 P_LANGUAGE in varchar2
272 ) return boolean;
273 --
274 --
275 end ota_ent_bus;
[Home] [Help]