1 Package irc_cmc_bus as
2 /* $Header: ircmcrhi.pkh 120.0 2007/11/19 11:23:16 sethanga 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_communication_id
15 -- already exists.
16 --
17 -- In Arguments:
18 -- p_communication_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_communication_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_communication_id
48 -- already exists.
49 --
50 -- In Arguments:
51 -- p_communication_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_communication_id in number
67 ) RETURN varchar2;
68 --
69 -- ---------------------------------------------------------------------------
70 -- |----------------------------< chk_status >------------------|
71 -- ---------------------------------------------------------------------------
72 --
73 -- {Start Of Comments}
74 --
75 -- Description:
76 -- This process validates that 'status' exists in the lookup
77 -- IRC_COMM_STATUS
78 --
79 -- Pre Conditions:
80 -- None.
81 --
82 -- In Parameters:
83 -- status varchar2(50) communication status
84 -- communication_id number(15) PK of irc_communications
85 -- effective_date date date record effective
86 -- object_version_number number(9) version of row
87 --
88 -- Post Success:
89 -- Processing continues.
90 --
91 -- Post Failure:
92 -- An application error will be raised for the following faliure conditions:
93 -- 1: p_status does not exist in lookup IRC_COMM_STATUS
94 --
95 -- Access Status:
96 -- Internal Table Handler Use Only.
97 Procedure chk_status(p_status in varchar2,
98 p_communication_id in number,
99 p_effective_date in date,
100 p_object_version_number in number);
101 --
102 -- ----------------------------------------------------------------------------
103 -- |-----------------------------< chk_object_id >-----------------------------|
104 -- ----------------------------------------------------------------------------
105 --
106 -- {Start Of Comments}
107 --
108 -- Description:
109 -- This procedure is used to ensure -
110 -- 1) that object_id exists in PER_ALL_ASSIGNMENTS_F
111 -- when the object_type is 'APPL'
112 -- 2) that combination of (object_id,object_type) is
113 -- unique.
114 --
115 -- Pre Conditions:
116 --
117 -- In Arguments:
118 -- p_object_id
119 -- p_object_type
120 --
121 -- Post Success:
122 -- Processing continues if object_id is valid.
123 --
124 -- Post Failure:
125 -- An application error is raised if object_id is invalid.
126 --
127 -- {End Of Comments}
128 -- ----------------------------------------------------------------------------
129 Procedure chk_object_id
130 (p_object_id in irc_communications.object_id%TYPE,
131 p_object_type in irc_communications.object_type%TYPE
132 ) ;
133 --
134 -- ----------------------------------------------------------------------------
135 -- |-----------------------------< chk_object_type >-----------------------------|
136 -- ----------------------------------------------------------------------------
137 --
138 -- {Start Of Comments}
139 --
140 -- Description:
141 -- This procedure is used to ensure that object_type has one of the following
142 -- values :
143 -- 'APPL'
144 --
145 -- Pre Conditions:
146 --
147 -- In Arguments:
148 -- p_object_type
149 --
150 -- Post Success:
151 -- Processing continues if object_type is valid.
152 --
153 -- Post Failure:
154 -- An application error is raised if object_type is invalid.
155 --
156 -- {End Of Comments}
157 -- ----------------------------------------------------------------------------
158 Procedure chk_object_type
159 (p_object_type in irc_communications.object_type%TYPE
160 ) ;
161 --
162 -- ----------------------------------------------------------------------------
163 -- |---------------------------< insert_update_validate >----------------------------|
164 -- ----------------------------------------------------------------------------
165 -- {Start of comments}
166 --
167 -- Description:
168 -- This procedure groups calls to various business-rules validation procedures
169 -- which are commonly called by insert_validate and update_validate procedures.
170 --
171 -- Prerequisites:
172 -- This private procedure is called from insert_validate and update_validate
173 -- procedures.
174 --
175 -- In Parameters:
176 -- A Pl/Sql record structure.
177 --
178 -- Post Success:
179 -- Processing continues.
180 --
181 -- Post Failure:
182 -- If a business rules fails the error will not be handled by this procedure
183 -- unless explicity coded.
184 --
185 -- Access Status:
186 -- Internal Row Handler Use Only.
187 --
188 -- {End of comments}
189 -- ----------------------------------------------------------------------------
190 Procedure insert_update_validate
191 (p_effective_date in date
192 ,p_rec in irc_cmc_shd.g_rec_type
193 );
194 --
195 -- ----------------------------------------------------------------------------
196 -- |---------------------------< insert_validate >----------------------------|
197 -- ----------------------------------------------------------------------------
198 -- {Start of comments}
199 --
200 -- Description:
201 -- This procedure controls the execution of all insert business rules
202 -- validation.
203 --
204 -- Prerequisites:
205 -- This private procedure is called from ins procedure.
206 --
207 -- In Parameters:
208 -- A Pl/Sql record structure.
209 --
210 -- Post Success:
211 -- Processing continues.
212 --
213 -- Post Failure:
214 -- If a business rules fails the error will not be handled by this procedure
215 -- unless explicity coded.
216 --
217 -- Developer Implementation Notes:
218 -- For insert, your business rules should be executed from this procedure
219 -- and should ideally (unless really necessary) just be straight procedure
220 -- or function calls. Try and avoid using conditional branching logic.
221 --
222 -- Access Status:
223 -- Internal Row Handler Use Only.
224 --
225 -- {End of comments}
226 -- ----------------------------------------------------------------------------
227 Procedure insert_validate
228 (p_effective_date in date
229 ,p_rec in irc_cmc_shd.g_rec_type
230 );
231 --
232 -- ----------------------------------------------------------------------------
233 -- |---------------------------< update_validate >----------------------------|
234 -- ----------------------------------------------------------------------------
235 -- {Start Of Comments}
236 --
237 -- Description:
238 -- This procedure controls the execution of all update business rules
239 -- validation.
240 --
241 -- Prerequisites:
242 -- This private procedure is called from upd procedure.
243 --
244 -- In Parameters:
245 -- A Pl/Sql record structure.
246 --
247 -- Post Success:
248 -- Processing continues.
249 --
250 -- Post Failure:
251 -- If a business rules fails the error will not be handled by this procedure
252 -- unless explicity coded.
253 --
254 -- Access Status:
255 -- Internal Row Handler Use Only.
256 --
257 -- {End Of Comments}
258 -- ----------------------------------------------------------------------------
259 Procedure update_validate
260 (p_effective_date in date
261 ,p_rec in irc_cmc_shd.g_rec_type
262 );
263 --
264 -- ----------------------------------------------------------------------------
265 -- |---------------------------< delete_validate >----------------------------|
266 -- ----------------------------------------------------------------------------
267 -- {Start Of Comments}
268 --
269 -- Description:
270 -- This procedure controls the execution of all delete business rules
271 -- validation.
272 --
273 -- Prerequisites:
274 -- This private procedure is called from del procedure.
275 --
276 -- In Parameters:
277 -- A Pl/Sql record structure.
278 --
279 -- Post Success:
280 -- Processing continues.
281 --
282 -- Post Failure:
283 -- If a business rules fails the error will not be handled by this procedure
284 -- unless explicity coded.
285 --
286 -- Developer Implementation Notes:
287 -- For delete, your business rules should be executed from this procedure
288 -- and should ideally (unless really necessary) just be straight procedure
289 -- or function calls. Try and avoid using conditional branching logic.
290 --
291 -- Access Status:
292 -- Internal Row Handler Use Only.
293 --
294 -- {End Of Comments}
295 -- ----------------------------------------------------------------------------
296 Procedure delete_validate
297 (p_rec in irc_cmc_shd.g_rec_type
298 );
299 --
300 end irc_cmc_bus;
[Home] [Help]