1 Package pe_aei_bus AUTHID CURRENT_USER as
2 /* $Header: peaeirhi.pkh 120.0 2005/05/31 05:08:28 appldev noship $ */
3 -- ---------------------------------------------------------------------------
4 -- |----------------------< set_security_group_id >--------------------------|
5 -- ---------------------------------------------------------------------------
6 -- {Start Of Comments}
7 --
8 -- Description:
9 -- Sets the security_group_id in CLIENT_INFO for the appropriate business
10 -- group context.
11 --
12 -- Prerequisites:
13 -- The primary key identified by p_assignment_extra_info_id
14 -- already exists.
15 --
16 -- In Arguments:
17 -- p_assignment_extra_info_id
18 --
19 --
20 -- Post Success:
21 -- The security_group_id will be set in CLIENT_INFO.
22 --
23 -- Post Failure:
24 -- An error is raised if the value does not exist.
25 --
26 -- Access Status:
27 -- Internal Development Use Only.
28 --
29 -- {End Of Comments}
30 -- ---------------------------------------------------------------------------
31 /*
32 procedure set_security_group_id
33 (p_assignment_extra_info_id in number
34 );
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_assignment_extra_info_id
48 -- already exists.
49 --
50 -- In Arguments:
51 -- p_assignment_extra_info_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_assignment_extra_info_id in number
67 ) RETURN varchar2;
68 --
69 --
70 -- ----------------------------------------------------------------------------
71 -- |-----------------------< chk_assignment_info_type >-----------------------|
72 -- ----------------------------------------------------------------------------
73 -- {Start Of Comments}
74 --
75 -- Description:
76 -- Validates that the assignment information type exists in table
77 -- per_assignment_info_types where active_inactive_flag is 'Y'.
78 --
79 -- Pre Conditions:
80 -- Data must be existed in table per_assignment_info_types.
81 --
82 -- In Parameters:
83 -- p_information_type
84 -- p_assignment_id
85 --
86 -- Post Success:
87 -- Processing continues.
88 --
89 -- Post Failure:
90 -- An application error will be raised and processing is terminated.
91 --
92 -- Developer Implementation Notes:
93 -- For insert, your business rules should be executed from this procedure and
94 -- should ideally (unless really necessary) just be straight procedure or
95 -- function calls. Try and avoid using conditional branching logic.
96 --
97 -- Access Status:
98 -- Internal Table Handler Use Only.
99 --
100 -- {End Of Comments}
101 -- ----------------------------------------------------------------------------
102 Procedure chk_assignment_info_type
103 (
104 p_information_type in per_assignment_extra_info.information_type%type
105 );
106 --
107 -- ----------------------------------------------------------------------------
108 -- |---------------------------< Chk_assignment_id >----------------------------|
109 -- ----------------------------------------------------------------------------
110 -- {Start Of Comments}
111 --
112 -- Description:
113 -- Verify that the value in assignment_ID is in the per_assignments_f table.
114 --
115 -- Pre Conditions:
116 --
117 --
118 -- In Parameters:
119 -- p_assignment_id
120 --
121 -- Post Success:
122 -- Processing continues.
123 --
124 -- Post Failure:
125 -- An application error will be raised and processing is terminated.
126 --
127 -- Developer Implementation Notes:
128 -- For insert, your business rules should be executed from this procedure and
129 -- should ideally (unless really necessary) just be straight procedure or
130 -- function calls. Try and avoid using conditional branching logic.
131 --
132 -- Access Status:
133 -- Internal Table Handler Use Only.
134 --
135 -- {End Of Comments}
136 -- ----------------------------------------------------------------------------
137 Procedure chk_assignment_id
138 (
139 p_assignment_id in per_assignment_extra_info.assignment_id%type
140 );
141 --
142 -- ----------------------------------------------------------------------------
143 -- |-----------------------< chk_non_updateable_args >------------------------|
144 -- ----------------------------------------------------------------------------
145 -- {Start Of Comments}
146 --
147 -- Description:
148 -- Verify that the non updateable arguments not changed.
149 --
150 -- Pre Conditions:
151 --
152 --
153 -- In Parameters:
154 -- p_rec
155 --
156 -- Post Success:
157 -- Processing continues.
158 --
159 -- Post Failure:
160 -- An application error will be raised and processing is terminated.
161 --
162 -- Developer Implementation Notes:
163 -- For insert, your business rules should be executed from this procedure and
164 -- should ideally (unless really necessary) just be straight procedure or
165 -- function calls. Try and avoid using conditional branching logic.
166 --
167 -- Access Status:
168 -- Internal Table Handler Use Only.
169 --
170 -- {End Of Comments}
171 -- ----------------------------------------------------------------------------
172 Procedure chk_non_updateable_args (p_rec in pe_aei_shd.g_rec_type);
173 --
174 -- ----------------------------------------------------------------------------
175 -- |---------------------------< insert_validate >----------------------------|
176 -- ----------------------------------------------------------------------------
177 -- {Start Of Comments}
178 --
179 -- Description:
180 -- This procedure controls the execution of all insert business rules
181 -- validation.
182 --
183 -- Pre Conditions:
184 -- This private procedure is called from ins procedure.
185 --
186 -- In Parameters:
187 -- A Pl/Sql record structre.
188 --
189 -- Post Success:
190 -- Processing continues.
191 --
192 -- Post Failure:
193 -- If a business rules fails the error will not be handled by this procedure
194 -- unless explicity coded.
195 --
196 -- Developer Implementation Notes:
197 -- For insert, your business rules should be executed from this procedure and
198 -- should ideally (unless really necessary) just be straight procedure or
199 -- function calls. Try and avoid using conditional branching logic.
200 --
201 -- Access Status:
202 -- Internal Table Handler Use Only.
203 --
204 -- {End Of Comments}
205 -- ----------------------------------------------------------------------------
206 Procedure insert_validate(p_rec in pe_aei_shd.g_rec_type);
207 --
208 -- ----------------------------------------------------------------------------
209 -- |---------------------------< update_validate >----------------------------|
210 -- ----------------------------------------------------------------------------
211 -- {Start Of Comments}
212 --
213 -- Description:
214 -- This procedure controls the execution of all update business rules
215 -- validation.
216 --
217 -- Pre Conditions:
218 -- This private procedure is called from upd procedure.
219 --
220 -- In Parameters:
221 -- A Pl/Sql record structre.
222 --
223 -- Post Success:
224 -- Processing continues.
225 --
226 -- Post Failure:
227 -- If a business rules fails the error will not be handled by this procedure
228 -- unless explicity coded.
229 --
230 -- Developer Implementation Notes:
231 -- For update, your business rules should be executed from this procedure and
232 -- should ideally (unless really necessary) just be straight procedure or
233 -- function calls. Try and avoid using conditional branching logic.
234 --
235 -- Access Status:
236 -- Internal Table Handler Use Only.
237 --
238 -- {End Of Comments}
239 -- ----------------------------------------------------------------------------
240 Procedure update_validate(p_rec in pe_aei_shd.g_rec_type);
241 --
242 -- ----------------------------------------------------------------------------
243 -- |---------------------------< delete_validate >----------------------------|
244 -- ----------------------------------------------------------------------------
245 -- {Start Of Comments}
246 --
247 -- Description:
248 -- This procedure controls the execution of all delete business rules
249 -- validation.
250 --
251 -- Pre Conditions:
252 -- This private procedure is called from del procedure.
253 --
254 -- In Parameters:
255 -- A Pl/Sql record structre.
256 --
257 -- Post Success:
258 -- Processing continues.
259 --
260 -- Post Failure:
261 -- If a business rules fails the error will not be handled by this procedure
262 -- unless explicity coded.
263 --
264 -- Developer Implementation Notes:
265 -- For delete, your business rules should be executed from this procedure and
266 -- should ideally (unless really necessary) just be straight procedure or
267 -- function calls. Try and avoid using conditional branching logic.
268 --
269 -- Access Status:
270 -- Internal Table Handler Use Only.
271 --
272 -- {End Of Comments}
273 -- ----------------------------------------------------------------------------
274 Procedure delete_validate(p_rec in pe_aei_shd.g_rec_type);
275 --
276 end pe_aei_bus;
[Home] [Help]