1 Package pqp_vre_bus as
2 /* $Header: pqvrerhi.pkh 120.0.12010000.1 2008/07/28 11:26:09 appldev ship $ */
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 --
13 -- Prerequisites:
14 -- The primary key identified by p_vehicle_repository_id
15 -- already exists.
16 --
17 -- In Arguments:
18 -- p_vehicle_repository_id
19 --
20 --
21 -- Post Success:
22 -- The security_group_id will be set in CLIENT_INFO.
23 --
24 -- Post Failure:
25 -- An error is raised if the value does not exist.
26 --
27 -- Access Status:
28 -- Internal Development Use Only.
29 --
30 -- {End Of Comments}
31 -- ---------------------------------------------------------------------------
32 procedure set_security_group_id
33 (p_vehicle_repository_id IN NUMBER
34 ,p_associated_column1 IN VARCHAR2 DEFAULT null
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_vehicle_repository_id
48 -- already exists.
49 --
50 -- In Arguments:
51 -- p_vehicle_repository_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_vehicle_repository_id IN NUMBER
67 ) RETURN varchar2;
68 --
69 --
70 --
71 -- ---------------------------------------------------------------------------
72 -- |---------------------< pqp_get_config_value >----------------------------|
73 -- ---------------------------------------------------------------------------
74 -- {Start Of Comments}
75 --
76 -- Description:
77 -- Returns the configuration value for businessGroupId/legistionId
78 --
79 -- Prerequisites:
80 -- The primary key identified by p_vehicle_repository_id
81 -- already exists.
82 --
83 -- In Arguments:
84 -- p_business_group_id ,p_legislation_code,p_seg_col_name
85 -- p_table_name,p_information_category
86 --
87 --
88 -- Post Success:
89 -- The Configuration value will be returned.
90 --
91 -- Post Failure:
92 -- An error is raised if the value does not exist.
93 --
94 -- Access Status:
95 -- Internal Development Use Only.
96 --
97 -- {End Of Comments}
98 -- ---------------------------------------------------------------------------
99 FUNCTION pqp_get_config_value (
100 p_business_group_id IN NUMBER,
101 p_legislation_code IN VARCHAR2,
102 p_seg_col_name IN VARCHAR2,
103 p_table_name IN VARCHAR2,
104 p_information_category IN VARCHAR2 )
105 RETURN VARCHAR2;
106 --
107 --
108 --
109
110 -- ---------------------------------------------------------------------------
111 -- |---------------------< get_uom_fiscal_ratings >-------------------------|
112 -- ---------------------------------------------------------------------------
113 -- {Start Of Comments}
114 --
115 -- Description:
116 -- Returns the fiscal ratings for businessGroupId
117 --
118 -- Prerequisites:
119 -- The primary key identified by p_business_group_id
120 -- already exists.
121 --
122 -- In Arguments:
123 -- p_business_group_id
124 --
125 --
126 -- Post Success:
127 -- The fiscal rating value will be returned.
128 --
129 -- Post Failure:
130 -- An error is raised if the value does not exist.
131 --
132 -- Access Status:
133 -- Internal Development Use Only.
134 --
135 -- {End Of Comments}
136 -- ---------------------------------------------------------------------------
137 PROCEDURE get_uom_fiscal_ratings
138 (p_business_group_id IN NUMBER
139 ,p_meaning OUT NOCOPY VARCHAR2);
140 --
141 -- ---------------------------------------------------------------------------
142 -- |---------------------< get_legislation_code >-------------------------|
143 -- ---------------------------------------------------------------------------
144 -- {Start Of Comments}
145 --
146 -- Description:
147 -- Return the legislation code for a business groupId
148 --
149 -- In Arguments:
150 -- business_group_id
151 --
152 --
153 -- Post Success:
154 -- The business group's legislation code will be returned.
155 --
156 -- Post Failure:
157 -- An error is raised if the value does not exist.
158 --
159 -- Access Status:
160 -- Internal Development Use Only.
161 --
162 -- {End Of Comments}
163 -- ---------------------------------------------------------------------------
164 FUNCTION get_legislation_code
165 (p_business_group_id IN NUMBER) RETURN VARCHAR2;
166 --
167 --
168 -- ----------------------------------------------------------------------------
169 -- |---------------------------< insert_validate >----------------------------|
170 -- ----------------------------------------------------------------------------
171 -- {Start Of Comments}
172 --
173 -- Description:
174 -- This procedure controls the execution of all insert business rules
175 -- validation.
176 --
177 -- Prerequisites:
178 -- This private procedure is called from ins procedure.
179 --
180 -- In Parameters:
181 -- A Pl/Sql record structre.
182 --
183 -- Post Success:
184 -- Processing continues.
185 --
186 -- Post Failure:
187 -- If a business rules fails the error will not be handled by this procedure
188 -- unless explicity coded.
189 --
190 -- Developer Implementation Notes:
191 -- For insert, your business rules should be executed from this procedure and
192 -- should ideally (unless really necessary) just be straight procedure or
193 -- function calls. Try and avoid using conditional branching logic.
194 --
195 -- Access Status:
196 -- Internal Row Handler Use Only.
197 --
198 -- {End Of Comments}
199 -- ----------------------------------------------------------------------------
200 PROCEDURE insert_validate
201 (p_rec IN pqp_vre_shd.g_rec_type
202 ,p_effective_date IN DATE
203 ,p_datetrack_mode IN VARCHAR2
204 ,p_validation_start_date IN DATE
205 ,p_validation_end_date IN DATE
206 );
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 -- Prerequisites:
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 Row Handler Use Only.
237 --
238 -- {End Of Comments}
239 -- ----------------------------------------------------------------------------
240 PROCEDURE update_validate
241 (p_rec IN pqp_vre_shd.g_rec_type
242 ,p_effective_date IN DATE
243 ,p_datetrack_mode IN VARCHAR2
244 ,p_validation_start_date IN DATE
245 ,p_validation_end_date IN DATE
246 );
247 --
248 -- ----------------------------------------------------------------------------
249 -- |---------------------------< delete_validate >----------------------------|
250 -- ----------------------------------------------------------------------------
251 -- {Start Of Comments}
252 --
253 -- Description:
254 -- This procedure controls the execution of all delete business rules
255 -- validation.
256 --
257 -- Prerequisites:
258 -- This private procedure is called from del procedure.
259 --
260 -- In Parameters:
261 -- A Pl/Sql record structure.
262 --
263 -- Post Success:
264 -- Processing continues.
265 --
266 -- Post Failure:
267 -- If a business rules fails the error will not be handled by this procedure
268 -- unless explicity coded.
269 --
270 -- Developer Implementation Notes:
271 -- For delete, your business rules should be executed from this procedure and
272 -- should ideally (unless really necessary) just be straight procedure or
273 -- function calls. Try and avoid using conditional branching logic.
274 --
275 -- Access Status:
276 -- Internal Row Handler Use Only.
277 --
278 -- {End Of Comments}
279 -- ----------------------------------------------------------------------------
280 PROCEDURE delete_validate
281 (p_rec IN pqp_vre_shd.g_rec_type
282 ,p_effective_date IN DATE
283 ,p_datetrack_mode IN VARCHAR2
284 ,p_validation_start_date IN DATE
285 ,p_validation_end_date IN DATE
286 );
287 --
288 end pqp_vre_bus;
[Home] [Help]