1 Package pay_blt_bus AUTHID CURRENT_USER as
2 /* $Header: pybltrhi.pkh 120.0 2005/05/29 03:22 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_type_id
17 -- already exists.
18 --
19 -- In Arguments:
20 -- p_balance_type_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_type_id in number
38 ,p_associated_column1 in varchar2 default null
39 );
40 --
41 --
42 -- ---------------------------------------------------------------------------
43 -- |---------------------< recreate_db_items >-------------------------------|
44 -- ---------------------------------------------------------------------------
45 -- {Start Of Comments}
46 --
47 -- Description:
48 -- this procedure recreate the database item for balance when ever balance
49 -- name is changed.
50 --
51 -- Prerequisites:
52 --
53 -- In Arguments:
54 -- p_balance_type_id
55 --
56 -- Post Success:
57 -- The database item is recreated
58 --
59 -- Post Failure:
60 -- An error is raised.
61 --
62 -- Access Status:
63 -- Internal Development Use Only.
64 --
65 -- {End Of Comments}
66 -- ---------------------------------------------------------------------------
67
68 Procedure recreate_db_items
69 (p_balance_type_id in number
70 );
71 -- ---------------------------------------------------------------------------
72 -- |---------------------< insert_primary_balance_feed >---------------------|
73 -- ---------------------------------------------------------------------------
74 -- {Start Of Comments}
75 --
76 -- Description:
77 -- this procedure automatically insert the associated feed if
78 -- primary balance is inserted.
79 --
80 -- Prerequisites:
81 --
82 -- In Arguments:
83 -- p_effective_date
84 -- p_business_group_id
85 -- p_balance_type_id
86 -- p_input_value_id
87 --
88 --
89 -- Post Success:
90 -- The associated feed is inserted in corresponding table
91 --
92 -- Post Failure:
93 -- An error is raised.
94 --
95 -- Access Status:
96 -- Internal Development Use Only.
97 --
98 -- {End Of Comments}
99 -- ---------------------------------------------------------------------------
100
101 procedure insert_primary_balance_feed
102 ( p_effective_date in date
103 ,p_business_group_id in number
104 ,p_balance_type_id in number
105 ,p_input_value_id in number
106 );
107
108 -- ---------------------------------------------------------------------------
109 -- |---------------------< return_legislation_code >-------------------------|
110 -- ---------------------------------------------------------------------------
111 -- {Start Of Comments}
112 --
113 -- Description:
114 -- Return the legislation code for a specific primary key value
115 --
116 -- Prerequisites:
117 -- The primary key identified by p_balance_type_id
118 -- already exists.
119 --
120 -- In Arguments:
121 -- p_balance_type_id
122 --
123 --
124 -- Post Success:
125 -- The business group's legislation code will be returned.
126 --
127 -- Post Failure:
128 -- An error is raised if the value does not exist.
129 --
130 -- Access Status:
131 -- Internal Development Use Only.
132 --
133 -- {End Of Comments}
134 -- ---------------------------------------------------------------------------
135 FUNCTION return_legislation_code
136 (p_balance_type_id in number
137 ) RETURN varchar2;
138 --
139 --
140 -- ----------------------------------------------------------------------------
141 -- |---------------------------< insert_validate >----------------------------|
142 -- ----------------------------------------------------------------------------
143 -- {Start of comments}
144 --
145 -- Description:
146 -- This procedure controls the execution of all insert business rules
147 -- validation.
148 --
149 -- Prerequisites:
150 -- This private procedure is called from ins procedure.
151 --
152 -- In Parameters:
153 -- A Pl/Sql record structure.
154 --
155 -- Post Success:
156 -- Processing continues.
157 --
158 -- Post Failure:
159 -- If a business rules fails the error will not be handled by this procedure
160 -- unless explicity coded.
161 --
162 -- Developer Implementation Notes:
163 -- For insert, your business rules should be executed from this procedure
164 -- and should ideally (unless really necessary) just be straight procedure
165 -- or function calls. Try and avoid using conditional branching logic.
166 --
167 -- Access Status:
168 -- Internal Row Handler Use Only.
169 --
170 -- {End of comments}
171 -- ----------------------------------------------------------------------------
172 Procedure insert_validate
173 (p_effective_date in date
174 ,p_rec in pay_blt_shd.g_rec_type
175 );
176 --
177 -- ----------------------------------------------------------------------------
178 -- |---------------------------< update_validate >----------------------------|
179 -- ----------------------------------------------------------------------------
180 -- {Start Of Comments}
181 --
182 -- Description:
183 -- This procedure controls the execution of all update business rules
184 -- validation.
185 --
186 -- Prerequisites:
187 -- This private procedure is called from upd procedure.
188 --
189 -- In Parameters:
190 -- A Pl/Sql record structure.
191 --
192 -- Post Success:
193 -- Processing continues.
194 --
195 -- Post Failure:
196 -- If a business rules fails the error will not be handled by this procedure
197 -- unless explicity coded.
198 --
199 -- Access Status:
200 -- Internal Row Handler Use Only.
201 --
202 -- {End Of Comments}
203 -- ----------------------------------------------------------------------------
204 Procedure update_validate
205 (p_effective_date in date
206 ,p_rec in pay_blt_shd.g_rec_type
207 ,p_balance_name_warning out nocopy number
208 );
209 --
210 -- ----------------------------------------------------------------------------
211 -- |---------------------------< delete_validate >----------------------------|
212 -- ----------------------------------------------------------------------------
213 -- {Start Of Comments}
214 --
215 -- Description:
216 -- This procedure controls the execution of all delete business rules
217 -- validation.
218 --
219 -- Prerequisites:
220 -- This private procedure is called from del procedure.
221 --
222 -- In Parameters:
223 -- A Pl/Sql record structure.
224 --
225 -- Post Success:
226 -- Processing continues.
227 --
228 -- Post Failure:
229 -- If a business rules fails the error will not be handled by this procedure
230 -- unless explicity coded.
231 --
232 -- Developer Implementation Notes:
233 -- For delete, your business rules should be executed from this procedure
234 -- and should ideally (unless really necessary) just be straight procedure
235 -- or function calls. Try and avoid using conditional branching logic.
236 --
237 -- Access Status:
238 -- Internal Row Handler Use Only.
239 --
240 -- {End Of Comments}
241 -- ----------------------------------------------------------------------------
242 Procedure delete_validate
243 (p_rec in pay_blt_shd.g_rec_type
244 );
245 --
246 end pay_blt_bus;
[Home] [Help]