1 Package Body pqp_gds_upd as
2 /* $Header: pqgdsrhi.pkb 120.0 2005/10/28 07:32 rvishwan noship $ */
3 --
4 -- ----------------------------------------------------------------------------
5 -- | Private Global Definitions |
6 -- ----------------------------------------------------------------------------
7 --
8 g_package varchar2(33) := ' pqp_gds_upd.'; -- Global package name
9 --
10 -- ----------------------------------------------------------------------------
11 -- |------------------------------< update_dml >------------------------------|
12 -- ----------------------------------------------------------------------------
13 -- {Start Of Comments}
14 --
15 -- Description:
16 -- This procedure controls the actual dml update logic. The processing of
17 -- this procedure is:
18 -- 1) Increment the object_version_number by 1 if the object_version_number
19 -- is defined as an attribute for this entity.
20 -- 2) To set and unset the g_api_dml status as required (as we are about to
21 -- perform dml).
22 -- 3) To update the specified row in the schema using the primary key in
23 -- the predicates.
24 -- 4) To trap any constraint violations that may have occurred.
25 -- 5) To raise any other errors.
26 --
27 -- Prerequisites:
28 -- This is an internal private procedure which must be called from the upd
29 -- procedure.
30 --
31 -- In Parameters:
32 -- A Pl/Sql record structre.
33 --
34 -- Post Success:
35 -- The specified row will be updated in the schema.
36 --
37 -- Post Failure:
38 -- On the update dml failure it is important to note that we always reset the
39 -- g_api_dml status to false.
40 -- If a check, unique or parent integrity constraint violation is raised the
41 -- constraint_error procedure will be called.
42 -- If any other error is reported, the error will be raised after the
43 -- g_api_dml status is reset.
44 --
45 -- Developer Implementation Notes:
46 -- The update 'set' attribute list should be modified if any of your
47 -- attributes are not updateable.
48 --
49 -- Access Status:
50 -- Internal Row Handler Use Only.
51 --
52 -- {End Of Comments}
53 -- ----------------------------------------------------------------------------
54 Procedure update_dml
55 (p_rec in out nocopy pqp_gds_shd.g_rec_type
56 ) is
57 --
58 l_proc varchar2(72) := g_package||'update_dml';
59 --
60 Begin
61 hr_utility.set_location('Entering:'||l_proc, 5);
62 --
63 -- Increment the object version
64 p_rec.object_version_number := p_rec.object_version_number + 1;
65 --
66 pqp_gds_shd.g_api_dml := true; -- Set the api dml status
67 --
68 -- Update the pqp_gap_duration_summary Row
69 --
70 update pqp_gap_duration_summary
71 set
72 gap_duration_summary_id = p_rec.gap_duration_summary_id
73 ,assignment_id = p_rec.assignment_id
74 ,gap_absence_plan_id = p_rec.gap_absence_plan_id
75 ,summary_type = p_rec.summary_type
76 ,gap_level = p_rec.gap_level
77 ,duration_in_days = p_rec.duration_in_days
78 ,duration_in_hours = p_rec.duration_in_hours
79 ,date_start = p_rec.date_start
80 ,date_end = p_rec.date_end
81 ,object_version_number = p_rec.object_version_number
82 where gap_duration_summary_id = p_rec.gap_duration_summary_id;
83 --
84 pqp_gds_shd.g_api_dml := false; -- Unset the api dml status
85 --
86 hr_utility.set_location(' Leaving:'||l_proc, 10);
87 --
88 Exception
89 When hr_api.check_integrity_violated Then
90 -- A check constraint has been violated
91 pqp_gds_shd.g_api_dml := false; -- Unset the api dml status
92 pqp_gds_shd.constraint_error
93 (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
94 When hr_api.parent_integrity_violated Then
95 -- Parent integrity has been violated
96 pqp_gds_shd.g_api_dml := false; -- Unset the api dml status
97 pqp_gds_shd.constraint_error
98 (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
99 When hr_api.unique_integrity_violated Then
100 -- Unique integrity has been violated
101 pqp_gds_shd.g_api_dml := false; -- Unset the api dml status
102 pqp_gds_shd.constraint_error
103 (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
104 When Others Then
105 pqp_gds_shd.g_api_dml := false; -- Unset the api dml status
106 Raise;
107 End update_dml;
108 --
109 -- ----------------------------------------------------------------------------
110 -- |------------------------------< pre_update >------------------------------|
111 -- ----------------------------------------------------------------------------
112 -- {Start Of Comments}
113 --
114 -- Description:
115 -- This private procedure contains any processing which is required before
116 -- the update dml.
117 --
118 -- Prerequisites:
119 -- This is an internal procedure which is called from the upd procedure.
120 --
121 -- In Parameters:
122 -- A Pl/Sql record structure.
123 --
124 -- Post Success:
125 -- Processing continues.
126 --
127 -- Post Failure:
128 -- If an error has occurred, an error message and exception wil be raised
129 -- but not handled.
130 --
131 -- Developer Implementation Notes:
132 -- Any pre-processing required before the update dml is issued should be
133 -- coded within this procedure. It is important to note that any 3rd party
134 -- maintenance should be reviewed before placing in this procedure.
135 --
136 -- Access Status:
137 -- Internal Row Handler Use Only.
138 --
139 -- {End Of Comments}
140 -- ----------------------------------------------------------------------------
141 Procedure pre_update
142 (p_rec in pqp_gds_shd.g_rec_type
143 ) is
144 --
145 l_proc varchar2(72) := g_package||'pre_update';
146 --
147 Begin
148 hr_utility.set_location('Entering:'||l_proc, 5);
149 --
150 hr_utility.set_location(' Leaving:'||l_proc, 10);
151 End pre_update;
152 --
153 -- ----------------------------------------------------------------------------
154 -- |-----------------------------< post_update >------------------------------|
155 -- ----------------------------------------------------------------------------
156 -- {Start Of Comments}
157 --
158 -- Description:
159 -- This private procedure contains any processing which is required after
160 -- the update dml.
161 --
162 -- Prerequisites:
163 -- This is an internal procedure which is called from the upd procedure.
164 --
165 -- In Parameters:
166 -- A Pl/Sql record structure.
167 --
168 -- Post Success:
169 -- Processing continues.
170 --
171 -- Post Failure:
172 -- If an error has occurred, an error message and exception will be raised
173 -- but not handled.
174 --
175 -- Developer Implementation Notes:
176 -- Any post-processing required after the update dml is issued should be
177 -- coded within this procedure. It is important to note that any 3rd party
178 -- maintenance should be reviewed before placing in this procedure.
179 --
180 -- Access Status:
181 -- Internal Row Handler Use Only.
182 --
183 -- {End Of Comments}
184 -- ----------------------------------------------------------------------------
185 Procedure post_update
186 (p_rec in pqp_gds_shd.g_rec_type
187 ) is
188 --
189 l_proc varchar2(72) := g_package||'post_update';
190 --
191 Begin
192 hr_utility.set_location('Entering:'||l_proc, 5);
193 begin
194 --
195 pqp_gds_rku.after_update
196 (p_gap_duration_summary_id
197 => p_rec.gap_duration_summary_id
198 ,p_assignment_id
199 => p_rec.assignment_id
200 ,p_gap_absence_plan_id
201 => p_rec.gap_absence_plan_id
202 ,p_summary_type
203 => p_rec.summary_type
204 ,p_gap_level
205 => p_rec.gap_level
206 ,p_duration_in_days
207 => p_rec.duration_in_days
208 ,p_duration_in_hours
209 => p_rec.duration_in_hours
210 ,p_date_start
211 => p_rec.date_start
212 ,p_date_end
213 => p_rec.date_end
214 ,p_object_version_number
215 => p_rec.object_version_number
216 ,p_assignment_id_o
217 => pqp_gds_shd.g_old_rec.assignment_id
218 ,p_gap_absence_plan_id_o
219 => pqp_gds_shd.g_old_rec.gap_absence_plan_id
220 ,p_summary_type_o
221 => pqp_gds_shd.g_old_rec.summary_type
222 ,p_gap_level_o
223 => pqp_gds_shd.g_old_rec.gap_level
224 ,p_duration_in_days_o
225 => pqp_gds_shd.g_old_rec.duration_in_days
226 ,p_duration_in_hours_o
227 => pqp_gds_shd.g_old_rec.duration_in_hours
228 ,p_date_start_o
229 => pqp_gds_shd.g_old_rec.date_start
230 ,p_date_end_o
231 => pqp_gds_shd.g_old_rec.date_end
232 ,p_object_version_number_o
233 => pqp_gds_shd.g_old_rec.object_version_number
234 );
235 --
236 exception
237 --
238 when hr_api.cannot_find_prog_unit then
239 --
240 hr_api.cannot_find_prog_unit_error
241 (p_module_name => 'PQP_GAP_DURATION_SUMMARY'
242 ,p_hook_type => 'AU');
243 --
244 end;
245 --
246 hr_utility.set_location(' Leaving:'||l_proc, 10);
247 End post_update;
248 --
249 -- ----------------------------------------------------------------------------
250 -- |-----------------------------< convert_defs >-----------------------------|
251 -- ----------------------------------------------------------------------------
252 -- {Start Of Comments}
253 --
254 -- Description:
255 -- The Convert_Defs procedure has one very important function:
256 -- It must return the record structure for the row with all system defaulted
257 -- values converted into its corresponding parameter value for update. When
258 -- we attempt to update a row through the Upd process , certain
259 -- parameters can be defaulted which enables flexibility in the calling of
260 -- the upd process (e.g. only attributes which need to be updated need to be
261 -- specified). For the upd process to determine which attributes
262 -- have NOT been specified we need to check if the parameter has a reserved
263 -- system default value. Therefore, for all parameters which have a
264 -- corresponding reserved system default mechanism specified we need to
265 -- check if a system default is being used. If a system default is being
266 -- used then we convert the defaulted value into its corresponding attribute
267 -- value held in the g_old_rec data structure.
268 --
269 -- Prerequisites:
270 -- This private function can only be called from the upd process.
271 --
272 -- In Parameters:
273 -- A Pl/Sql record structure.
274 --
275 -- Post Success:
276 -- The record structure will be returned with all system defaulted parameter
277 -- values converted into its current row attribute value.
278 --
279 -- Post Failure:
280 -- No direct error handling is required within this function. Any possible
281 -- errors within this procedure will be a PL/SQL value error due to
282 -- conversion of datatypes or data lengths.
283 --
284 -- Developer Implementation Notes:
285 -- None.
286 --
287 -- Access Status:
288 -- Internal Row Handler Use Only.
289 --
290 -- {End Of Comments}
291 -- ----------------------------------------------------------------------------
292 Procedure convert_defs
293 (p_rec in out nocopy pqp_gds_shd.g_rec_type
294 ) is
295 --
296 Begin
297 --
298 -- We must now examine each argument value in the
299 -- p_rec plsql record structure
300 -- to see if a system default is being used. If a system default
301 -- is being used then we must set to the 'current' argument value.
302 --
303 If (p_rec.assignment_id = hr_api.g_number) then
304 p_rec.assignment_id :=
305 pqp_gds_shd.g_old_rec.assignment_id;
306 End If;
307 If (p_rec.gap_absence_plan_id = hr_api.g_number) then
308 p_rec.gap_absence_plan_id :=
309 pqp_gds_shd.g_old_rec.gap_absence_plan_id;
310 End If;
311 If (p_rec.summary_type = hr_api.g_varchar2) then
312 p_rec.summary_type :=
313 pqp_gds_shd.g_old_rec.summary_type;
314 End If;
315 If (p_rec.gap_level = hr_api.g_varchar2) then
316 p_rec.gap_level :=
317 pqp_gds_shd.g_old_rec.gap_level;
318 End If;
319 If (p_rec.duration_in_days = hr_api.g_number) then
320 p_rec.duration_in_days :=
321 pqp_gds_shd.g_old_rec.duration_in_days;
322 End If;
323 If (p_rec.duration_in_hours = hr_api.g_number) then
324 p_rec.duration_in_hours :=
325 pqp_gds_shd.g_old_rec.duration_in_hours;
326 End If;
327 If (p_rec.date_start = hr_api.g_date) then
328 p_rec.date_start :=
329 pqp_gds_shd.g_old_rec.date_start;
330 End If;
331 If (p_rec.date_end = hr_api.g_date) then
332 p_rec.date_end :=
333 pqp_gds_shd.g_old_rec.date_end;
334 End If;
335 --
336 End convert_defs;
337 --
338 -- ----------------------------------------------------------------------------
339 -- |---------------------------------< upd >----------------------------------|
340 -- ----------------------------------------------------------------------------
341 Procedure upd
342 (p_rec in out nocopy pqp_gds_shd.g_rec_type
343 ) is
344 --
345 l_proc varchar2(72) := g_package||'upd';
346 --
347 Begin
348 hr_utility.set_location('Entering:'||l_proc, 5);
349 --
350 -- We must lock the row which we need to update.
351 --
352 pqp_gds_shd.lck
353 (p_rec.gap_duration_summary_id
354 ,p_rec.object_version_number
355 );
356 --
357 -- 1. During an update system defaults are used to determine if
358 -- arguments have been defaulted or not. We must therefore
359 -- derive the full record structure values to be updated.
360 --
361 -- 2. Call the supporting update validate operations.
362 --
363 convert_defs(p_rec);
364 pqp_gds_bus.update_validate
365 (p_rec
366 );
367 --
368 -- Call to raise any errors on multi-message list
369 hr_multi_message.end_validation_set;
370 --
371 -- Call the supporting pre-update operation
372 --
373 pqp_gds_upd.pre_update(p_rec);
374 --
375 -- Update the row.
376 --
377 pqp_gds_upd.update_dml(p_rec);
378 --
379 -- Call the supporting post-update operation
380 --
381 pqp_gds_upd.post_update
382 (p_rec
383 );
384 --
385 -- Call to raise any errors on multi-message list
386 hr_multi_message.end_validation_set;
387 End upd;
388 --
389 -- ----------------------------------------------------------------------------
390 -- |---------------------------------< upd >----------------------------------|
391 -- ----------------------------------------------------------------------------
392 Procedure upd
393 (p_gap_duration_summary_id in number
394 ,p_object_version_number in out nocopy number
395 ,p_assignment_id in number default hr_api.g_number
396 ,p_gap_absence_plan_id in number default hr_api.g_number
397 ,p_summary_type in varchar2 default hr_api.g_varchar2
398 ,p_gap_level in varchar2 default hr_api.g_varchar2
399 ,p_duration_in_days in number default hr_api.g_number
400 ,p_duration_in_hours in number default hr_api.g_number
401 ,p_date_start in date default hr_api.g_date
402 ,p_date_end in date default hr_api.g_date
403 ) is
404 --
405 l_rec pqp_gds_shd.g_rec_type;
406 l_proc varchar2(72) := g_package||'upd';
407 --
408 Begin
409 hr_utility.set_location('Entering:'||l_proc, 5);
410 --
411 -- Call conversion function to turn arguments into the
412 -- l_rec structure.
413 --
414 l_rec :=
415 pqp_gds_shd.convert_args
416 (p_gap_duration_summary_id
417 ,p_assignment_id
418 ,p_gap_absence_plan_id
419 ,p_summary_type
420 ,p_gap_level
421 ,p_duration_in_days
422 ,p_duration_in_hours
423 ,p_date_start
424 ,p_date_end
425 ,p_object_version_number
426 );
427 --
428 -- Having converted the arguments into the
429 -- plsql record structure we call the corresponding record
430 -- business process.
431 --
432 pqp_gds_upd.upd
433 (l_rec
434 );
435 p_object_version_number := l_rec.object_version_number;
436 --
437 hr_utility.set_location(' Leaving:'||l_proc, 10);
438 End upd;
439 --
440 end pqp_gds_upd;
[Home] [Help]