1 Package pay_apr_bus as
2 /* $Header: pyaprrhi.pkh 120.2 2006/12/04 13:29:21 abhargav 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 -- It is only valid to call this procedure when the primary key
13 -- is within a buisiness group context.
14 --
15 -- Prerequisites:
16 -- The primary key identified by p_process_id
17 -- already exists.
18 --
19 -- In Arguments:
20 -- p_process_id
21 --
22 --
23 -- Post Success:
24 -- The security_group_id will be set in CLIENT_INFO.
25 --
26 -- Post Failure:
27 -- An error is raised if the value does not exist.
28 -- An error is also raised when the primary key data is outside
29 -- of a buisiness group context.
30 --
31 -- Access Status:
32 -- Internal Development Use Only.
33 --
34 -- {End Of Comments}
35 -- ---------------------------------------------------------------------------
36 procedure set_security_group_id
37 (p_process_id in number
38 ,p_associated_column1 in varchar2 default null
39 );
40 --
41 --
42 -- ---------------------------------------------------------------------------
43 -- |---------------------< return_legislation_code >-------------------------|
44 -- ---------------------------------------------------------------------------
45 -- {Start Of Comments}
46 --
47 -- Description:
48 -- Return the legislation code for a specific primary key value
49 --
50 -- Prerequisites:
51 -- The primary key identified by p_process_id
52 -- already exists.
53 --
54 -- In Arguments:
55 -- p_process_id
56 --
57 --
58 -- Post Success:
59 -- The business group's legislation code will be returned.
60 --
61 -- Post Failure:
62 -- An error is raised if the value does not exist.
63 --
64 -- Access Status:
65 -- Internal Development Use Only.
66 --
67 -- {End Of Comments}
68 -- ---------------------------------------------------------------------------
69 FUNCTION return_legislation_code
70 (p_process_id in number
71 ) RETURN varchar2;
72 --
73 --
74 -- ---------------------------------------------------------------------------
75 -- |---------------------< chk_legislation_code >-------------------------|
76 -- ---------------------------------------------------------------------------
77 -- {Start Of Comments}
78 --
79 -- Description:
80 -- Check the legislation code is not null and is 'AU' or 'NZ'
81 --
82 -- Prerequisites:
83 --
84 -- In Arguments:
85 -- p_legislation_code
86 --
87 --
88 -- Post Success:
89 -- processing continues as no error is raised.
90 --
91 -- Post Failure:
92 -- An error is raised if the value of the legislation code is invalid.
93 --
94 -- Access Status:
95 -- Internal Development Use Only.
96 --
97 -- {End Of Comments}
98 -- ---------------------------------------------------------------------------
99 PROCEDURE chk_legislation_code
100 (p_legislation_code in varchar2
101 );
102 --
103 --
104 -- ---------------------------------------------------------------------------
105 -- |---------------------< chk_business_group_id >---------------------------|
106 -- ---------------------------------------------------------------------------
107 -- {Start Of Comments}
108 --
109 -- Description:
110 -- Check the business group id existl for choosen legislation code
111 --
112 -- Prerequisites:
113 --
114 -- In Arguments:
115 -- p_legislation_code
116 -- p_business_group_id
117 --
118 --
119 -- Post Success:
120 -- processing continues as no error is raised.
121 --
122 -- Post Failure:
123 -- An error is raised if mismatch the legislation code and business group id
124 --
125 -- Access Status:
126 -- Internal Development Use Only.
127 --
128 -- {End Of Comments}
129 -- ---------------------------------------------------------------------------
130 PROCEDURE chk_business_group_id
131 (p_legislation_code in varchar2
132 ,p_business_group_id in number
133 );
134 --
135 --
136 -- ---------------------------------------------------------------------------
137 -- |---------------------< chk_enabled_flag >--------------------------------|
138 -- ---------------------------------------------------------------------------
139 -- {Start Of Comments}
140 --
141 -- Description:
142 -- Check the field enabled_flag is 'Y' or 'N'
143 --
144 -- Prerequisites:
145 --
146 -- In Arguments:
147 -- p_enabled_flag
148 --
149 --
150 -- Post Success:
151 -- processing continues as no error is raised.
152 --
153 -- Post Failure:
154 -- An error is raised if the value of the enabled flag is invalid.
155 --
156 -- Access Status:
157 -- Internal Development Use Only.
158 --
159 -- {End Of Comments}
160 -- ---------------------------------------------------------------------------
161 PROCEDURE chk_enabled_flag
162 (p_enabled_flag in varchar2
163 );
164 --
165 -- ----------------------------------------------------------------------------
166 -- |---------------------------< insert_validate >----------------------------|
167 -- ----------------------------------------------------------------------------
168 -- {Start of comments}
169 --
170 -- Description:
171 -- This procedure controls the execution of all insert business rules
172 -- validation.
173 --
174 -- Prerequisites:
175 -- This private procedure is called from ins procedure.
176 --
177 -- In Parameters:
178 -- A Pl/Sql record structure.
179 --
180 -- Post Success:
181 -- Processing continues.
182 --
183 -- Post Failure:
184 -- If a business rules fails the error will not be handled by this procedure
185 -- unless explicity coded.
186 --
187 -- Developer Implementation Notes:
188 -- For insert, your business rules should be executed from this procedure
189 -- and should ideally (unless really necessary) just be straight procedure
190 -- or function calls. Try and avoid using conditional branching logic.
191 --
192 -- Access Status:
193 -- Internal Row Handler Use Only.
194 --
195 -- {End of comments}
196 -- ----------------------------------------------------------------------------
197 Procedure insert_validate
198 (p_rec in pay_apr_shd.g_rec_type
199 );
200 --
201 -- ----------------------------------------------------------------------------
202 -- |---------------------------< update_validate >----------------------------|
203 -- ----------------------------------------------------------------------------
204 -- {Start Of Comments}
205 --
206 -- Description:
207 -- This procedure controls the execution of all update business rules
208 -- validation.
209 --
210 -- Prerequisites:
211 -- This private procedure is called from upd procedure.
212 --
213 -- In Parameters:
214 -- A Pl/Sql record structure.
215 --
216 -- Post Success:
217 -- Processing continues.
218 --
219 -- Post Failure:
220 -- If a business rules fails the error will not be handled by this procedure
221 -- unless explicity coded.
222 --
223 -- Access Status:
224 -- Internal Row Handler Use Only.
225 --
226 -- {End Of Comments}
227 -- ----------------------------------------------------------------------------
228 Procedure update_validate
229 (p_rec in pay_apr_shd.g_rec_type
230 );
231 --
232 -- ----------------------------------------------------------------------------
233 -- |---------------------------< delete_validate >----------------------------|
234 -- ----------------------------------------------------------------------------
235 -- {Start Of Comments}
236 --
237 -- Description:
238 -- This procedure controls the execution of all delete business rules
239 -- validation.
240 --
241 -- Prerequisites:
242 -- This private procedure is called from del 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 -- Developer Implementation Notes:
255 -- For delete, your business rules should be executed from this procedure
256 -- and should ideally (unless really necessary) just be straight procedure
257 -- or function calls. Try and avoid using conditional branching logic.
258 --
259 -- Access Status:
260 -- Internal Row Handler Use Only.
261 --
262 -- {End Of Comments}
263 -- ----------------------------------------------------------------------------
264 Procedure delete_validate
265 (p_rec in pay_apr_shd.g_rec_type
266 );
267 --
268 end pay_apr_bus;
[Home] [Help]