1 Package pay_pba_bus as
2 /* $Header: pypbarhi.pkh 120.0 2005/05/29 07:18:02 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 -- 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_balance_attribute_id
17 -- already exists.
18 --
19 -- In Arguments:
20 -- p_balance_attribute_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_balance_attribute_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_balance_attribute_id
52 -- already exists.
53 --
54 -- In Arguments:
55 -- p_balance_attribute_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_balance_attribute_id in number
71 ) RETURN varchar2;
72 --
73 -- ----------------------------------------------------------------------------
74 -- |---------------------------< chk_attribute_id >---------------------------|
75 -- ----------------------------------------------------------------------------
76 -- {Start Of Comments}
77 --
78 -- Description:
79 -- This procedure is used to check the validity of the attribute_id
80 -- entered. The following rules apply
81 --
82 -- Mode Attribute_id Result
83 -- ------ ----------- ---------------------------------------------------
84 -- USER USER USER row in balance_attributes
85 -- USER STARTUP USER row in balance_attributes
86 -- USER GENERIC USER row in balance_attributes
87 -- STARTUP USER Error - This mode cannot access USER attributes
88 -- STARTUP STARTUP STARTUP row in balance_attributes
89 -- STARTUP GENERIC STARTUP row in balance_attributes
90 -- GENERIC USER Error - This mode cannot access USER attributes
91 -- GENERIC STARTUP Error - This mode cannot access STARTUP attributes
92 -- GENERIC GENERIC GENERIC row in balance_attributes
93 --
94 -- Pre Conditions:
95 -- g_old_rec has been populated with details of the values currently in
96 -- the database.
97 --
98 -- In Arguments:
99 -- p_rec has been populated with the updated values the user would like the
100 -- record set to.
101 --
102 -- Post Success:
103 -- Processing continues if a valid attribute_id exists.
104 --
105 -- Post Failure:
106 -- An application error is raised if the attribute_id does not exist.
107 -- entered.
108 --
109 -- {End Of Comments}
110 -- ----------------------------------------------------------------------------
111 Procedure chk_attribute_id
112 (p_balance_attribute_id in number
113 ,p_attribute_id in number
114 ,p_business_group_id in number default null
115 ,p_legislation_code in varchar2 default null);
116 --
117 -- ----------------------------------------------------------------------------
118 -- |-----------------------------< chk_def_bal_id >---------------------------|
119 -- ----------------------------------------------------------------------------
120 -- {Start Of Comments}
121 --
122 -- Description:
123 -- This procedure is used to check the validity of the attribute_id
124 -- entered. The following rules apply
125 --
126 -- Mode Attribute_id Result
127 -- ------ ----------- ---------------------------------------------------
128 -- USER USER USER row in balance_attributes
129 -- USER STARTUP USER row in balance_attributes
130 -- USER GENERIC USER row in balance_attributes
131 -- STARTUP USER Error - This mode cannot access USER def balances
132 -- STARTUP STARTUP STARTUP row in balance_attributes
133 -- STARTUP GENERIC STARTUP row in balance_attributes
134 -- GENERIC USER Error - This mode cannot access USER def balances
135 -- GENERIC STARTUP Error - This mode cannot access STARTUP def balances
136 -- GENERIC GENERIC GENERIC row in balance_attributes
137 --
138 -- Pre Conditions:
139 -- g_old_rec has been populated with details of the values currently in
140 -- the database.
141 --
142 -- In Arguments:
143 -- p_rec has been populated with the updated values the user would like the
144 -- record set to.
145 --
146 -- Post Success:
147 -- Processing continues if a valid defined_balance_id exists.
148 --
149 -- Post Failure:
150 -- An application error is raised if the defined_balance_id does not exist.
151 --
152 -- {End Of Comments}
153 -- ----------------------------------------------------------------------------
154 Procedure chk_def_bal_id
155 (p_balance_attribute_id in number
156 ,p_defined_balance_id in number
157 ,p_business_group_id in number default null
158 ,p_legislation_code in varchar2 default null);
159 --
160 -- ----------------------------------------------------------------------------
161 -- |---------------------------< insert_validate >----------------------------|
162 -- ----------------------------------------------------------------------------
163 -- {Start of comments}
164 --
165 -- Description:
166 -- This procedure controls the execution of all insert business rules
167 -- validation.
168 --
169 -- Prerequisites:
170 -- This private procedure is called from ins procedure.
171 --
172 -- In Parameters:
173 -- A Pl/Sql record structure.
174 --
175 -- Post Success:
176 -- Processing continues.
177 --
178 -- Post Failure:
179 -- If a business rules fails the error will not be handled by this procedure
180 -- unless explicity coded.
181 --
182 -- Developer Implementation Notes:
183 -- For insert, your business rules should be executed from this procedure
184 -- and should ideally (unless really necessary) just be straight procedure
185 -- or function calls. Try and avoid using conditional branching logic.
186 --
187 -- Access Status:
188 -- Internal Row Handler Use Only.
189 --
190 -- {End of comments}
191 -- ----------------------------------------------------------------------------
192 Procedure insert_validate
193 (p_rec in pay_pba_shd.g_rec_type
194 );
195 --
196 -- ----------------------------------------------------------------------------
197 -- |---------------------------< delete_validate >----------------------------|
198 -- ----------------------------------------------------------------------------
199 -- {Start Of Comments}
200 --
201 -- Description:
202 -- This procedure controls the execution of all delete business rules
203 -- validation.
204 --
205 -- Prerequisites:
206 -- This private procedure is called from del procedure.
207 --
208 -- In Parameters:
209 -- A Pl/Sql record structure.
210 --
211 -- Post Success:
212 -- Processing continues.
213 --
214 -- Post Failure:
215 -- If a business rules fails the error will not be handled by this procedure
216 -- unless explicity coded.
217 --
218 -- Developer Implementation Notes:
219 -- For delete, your business rules should be executed from this procedure
220 -- and should ideally (unless really necessary) just be straight procedure
221 -- or function calls. Try and avoid using conditional branching logic.
222 --
223 -- Access Status:
224 -- Internal Row Handler Use Only.
225 --
226 -- {End Of Comments}
227 -- ----------------------------------------------------------------------------
228 Procedure delete_validate
229 (p_rec in pay_pba_shd.g_rec_type
230 );
231 --
232 end pay_pba_bus;
[Home] [Help]