1 Package pay_amo_bus as
2 /* $Header: pyamorhi.pkh 120.2 2006/12/04 13:24:47 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_module_id
17 -- already exists.
18 --
19 -- In Arguments:
20 -- p_module_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_module_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_module_id
52 -- already exists.
53 --
54 -- In Arguments:
55 -- p_module_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_module_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 -- |---------------------------< insert_validate >----------------------------|
138 -- ----------------------------------------------------------------------------
139 -- {Start of comments}
140 --
141 -- Description:
142 -- This procedure controls the execution of all insert business rules
143 -- validation.
144 --
145 -- Prerequisites:
146 -- This private procedure is called from ins procedure.
147 --
148 -- In Parameters:
149 -- A Pl/Sql record structure.
150 --
151 -- Post Success:
152 -- Processing continues.
153 --
154 -- Post Failure:
155 -- If a business rules fails the error will not be handled by this procedure
156 -- unless explicity coded.
157 --
158 -- Developer Implementation Notes:
159 -- For insert, your business rules should be executed from this procedure
160 -- and should ideally (unless really necessary) just be straight procedure
161 -- or function calls. Try and avoid using conditional branching logic.
162 --
163 -- Access Status:
164 -- Internal Row Handler Use Only.
165 --
166 -- {End of comments}
167 -- ----------------------------------------------------------------------------
168 Procedure insert_validate
169 (p_rec in pay_amo_shd.g_rec_type
170 );
171 --
172 -- ----------------------------------------------------------------------------
173 -- |---------------------------< update_validate >----------------------------|
174 -- ----------------------------------------------------------------------------
175 -- {Start Of Comments}
176 --
177 -- Description:
178 -- This procedure controls the execution of all update business rules
179 -- validation.
180 --
181 -- Prerequisites:
182 -- This private procedure is called from upd procedure.
183 --
184 -- In Parameters:
185 -- A Pl/Sql record structure.
186 --
187 -- Post Success:
188 -- Processing continues.
189 --
190 -- Post Failure:
191 -- If a business rules fails the error will not be handled by this procedure
192 -- unless explicity coded.
193 --
194 -- Access Status:
195 -- Internal Row Handler Use Only.
196 --
197 -- {End Of Comments}
198 -- ----------------------------------------------------------------------------
199 Procedure update_validate
200 (p_rec in pay_amo_shd.g_rec_type
201 );
202 --
203 -- ----------------------------------------------------------------------------
204 -- |---------------------------< delete_validate >----------------------------|
205 -- ----------------------------------------------------------------------------
206 -- {Start Of Comments}
207 --
208 -- Description:
209 -- This procedure controls the execution of all delete business rules
210 -- validation.
211 --
212 -- Prerequisites:
213 -- This private procedure is called from del procedure.
214 --
215 -- In Parameters:
216 -- A Pl/Sql record structure.
217 --
218 -- Post Success:
219 -- Processing continues.
220 --
221 -- Post Failure:
222 -- If a business rules fails the error will not be handled by this procedure
223 -- unless explicity coded.
224 --
225 -- Developer Implementation Notes:
226 -- For delete, your business rules should be executed from this procedure
227 -- and should ideally (unless really necessary) just be straight procedure
228 -- or function calls. Try and avoid using conditional branching logic.
229 --
230 -- Access Status:
231 -- Internal Row Handler Use Only.
232 --
233 -- {End Of Comments}
234 -- ----------------------------------------------------------------------------
235 Procedure delete_validate
236 (p_rec in pay_amo_shd.g_rec_type
237 );
238 --
239 end pay_amo_bus;
[Home] [Help]