1 Package Body ota_coi_upd as
2 /* $Header: otcoirhi.pkb 120.3 2005/08/12 02:46 pchandra noship $ */
3 --
4 -- ----------------------------------------------------------------------------
5 -- | Private Global Definitions |
6 -- ----------------------------------------------------------------------------
7 --
8 g_package varchar2(33) := ' ota_coi_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 ota_coi_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 --
67 --
68 -- Update the ota_chat_obj_inclusions Row
69 --
70 update ota_chat_obj_inclusions
71 set
72 chat_id = p_rec.chat_id
73 ,object_id = p_rec.object_id
74 ,object_type = p_rec.object_type
75 ,start_date_active = p_rec.start_date_active
76 ,end_date_active = p_rec.end_date_active
77 ,primary_flag = p_rec.primary_flag
78 ,object_version_number = p_rec.object_version_number
79 where chat_id = p_rec.chat_id
80 and object_id = p_rec.object_id
81 and object_type = p_rec.object_type;
82 --
83 --
84 --
85 hr_utility.set_location(' Leaving:'||l_proc, 10);
86 --
87 Exception
88 When hr_api.check_integrity_violated Then
89 -- A check constraint has been violated
90 --
91 ota_coi_shd.constraint_error
92 (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
93 When hr_api.parent_integrity_violated Then
94 -- Parent integrity has been violated
95 --
96 ota_coi_shd.constraint_error
97 (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
98 When hr_api.unique_integrity_violated Then
99 -- Unique integrity has been violated
100 --
101 ota_coi_shd.constraint_error
102 (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
103 When Others Then
104 --
105 Raise;
106 End update_dml;
107 --
108 -- ----------------------------------------------------------------------------
109 -- |------------------------------< pre_update >------------------------------|
110 -- ----------------------------------------------------------------------------
111 -- {Start Of Comments}
112 --
113 -- Description:
114 -- This private procedure contains any processing which is required before
115 -- the update dml.
116 --
117 -- Prerequisites:
118 -- This is an internal procedure which is called from the upd procedure.
119 --
120 -- In Parameters:
121 -- A Pl/Sql record structure.
122 --
123 -- Post Success:
124 -- Processing continues.
125 --
126 -- Post Failure:
127 -- If an error has occurred, an error message and exception wil be raised
128 -- but not handled.
129 --
130 -- Developer Implementation Notes:
131 -- Any pre-processing required before the update dml is issued should be
132 -- coded within this procedure. It is important to note that any 3rd party
133 -- maintenance should be reviewed before placing in this procedure.
134 --
135 -- Access Status:
136 -- Internal Row Handler Use Only.
137 --
138 -- {End Of Comments}
139 -- ----------------------------------------------------------------------------
140 Procedure pre_update
141 (p_rec in ota_coi_shd.g_rec_type
142 ) is
143 --
144 l_proc varchar2(72) := g_package||'pre_update';
145 --
146 Begin
147 hr_utility.set_location('Entering:'||l_proc, 5);
148 --
149 hr_utility.set_location(' Leaving:'||l_proc, 10);
150 End pre_update;
151 --
152 -- ----------------------------------------------------------------------------
153 -- |-----------------------------< post_update >------------------------------|
154 -- ----------------------------------------------------------------------------
155 -- {Start Of Comments}
156 --
157 -- Description:
158 -- This private procedure contains any processing which is required after
159 -- the update dml.
160 --
161 -- Prerequisites:
162 -- This is an internal procedure which is called from the upd procedure.
163 --
164 -- In Parameters:
165 -- A Pl/Sql record structure.
166 --
167 -- Post Success:
168 -- Processing continues.
169 --
170 -- Post Failure:
171 -- If an error has occurred, an error message and exception will be raised
172 -- but not handled.
173 --
174 -- Developer Implementation Notes:
175 -- Any post-processing required after the update dml is issued should be
176 -- coded within this procedure. It is important to note that any 3rd party
177 -- maintenance should be reviewed before placing in this procedure.
178 --
179 -- Access Status:
180 -- Internal Row Handler Use Only.
181 --
182 -- {End Of Comments}
183 -- ----------------------------------------------------------------------------
184 Procedure post_update
185 (p_effective_date in date
186 ,p_rec in ota_coi_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 ota_coi_rku.after_update
196 (p_effective_date => p_effective_date
197 ,p_chat_id
198 => p_rec.chat_id
199 ,p_object_id
200 => p_rec.object_id
201 ,p_object_type
202 => p_rec.object_type
203 ,p_start_date_active
204 => p_rec.start_date_active
205 ,p_end_date_active
206 => p_rec.end_date_active
207 ,p_primary_flag
208 => p_rec.primary_flag
209 ,p_object_version_number
210 => p_rec.object_version_number
211 ,p_start_date_active_o
212 => ota_coi_shd.g_old_rec.start_date_active
213 ,p_end_date_active_o
214 => ota_coi_shd.g_old_rec.end_date_active
215 ,p_primary_flag_o
216 => ota_coi_shd.g_old_rec.primary_flag
217 ,p_object_version_number_o
218 => ota_coi_shd.g_old_rec.object_version_number
219 );
220 --
221 exception
222 --
223 when hr_api.cannot_find_prog_unit then
224 --
225 hr_api.cannot_find_prog_unit_error
226 (p_module_name => 'OTA_CHAT_OBJ_INCLUSIONS'
227 ,p_hook_type => 'AU');
228 --
229 end;
230 --
231 hr_utility.set_location(' Leaving:'||l_proc, 10);
232 End post_update;
233 --
234 -- ----------------------------------------------------------------------------
235 -- |-----------------------------< convert_defs >-----------------------------|
236 -- ----------------------------------------------------------------------------
237 -- {Start Of Comments}
238 --
239 -- Description:
240 -- The Convert_Defs procedure has one very important function:
241 -- It must return the record structure for the row with all system defaulted
242 -- values converted into its corresponding parameter value for update. When
243 -- we attempt to update a row through the Upd process , certain
244 -- parameters can be defaulted which enables flexibility in the calling of
245 -- the upd process (e.g. only attributes which need to be updated need to be
246 -- specified). For the upd process to determine which attributes
247 -- have NOT been specified we need to check if the parameter has a reserved
248 -- system default value. Therefore, for all parameters which have a
249 -- corresponding reserved system default mechanism specified we need to
250 -- check if a system default is being used. If a system default is being
251 -- used then we convert the defaulted value into its corresponding attribute
252 -- value held in the g_old_rec data structure.
253 --
254 -- Prerequisites:
255 -- This private function can only be called from the upd process.
256 --
257 -- In Parameters:
258 -- A Pl/Sql record structure.
259 --
260 -- Post Success:
261 -- The record structure will be returned with all system defaulted parameter
262 -- values converted into its current row attribute value.
263 --
264 -- Post Failure:
265 -- No direct error handling is required within this function. Any possible
266 -- errors within this procedure will be a PL/SQL value error due to
267 -- conversion of datatypes or data lengths.
268 --
269 -- Developer Implementation Notes:
270 -- None.
271 --
272 -- Access Status:
273 -- Internal Row Handler Use Only.
274 --
275 -- {End Of Comments}
276 -- ----------------------------------------------------------------------------
277 Procedure convert_defs
278 (p_rec in out nocopy ota_coi_shd.g_rec_type
279 ) is
280 --
281 Begin
282 --
283 -- We must now examine each argument value in the
284 -- p_rec plsql record structure
285 -- to see if a system default is being used. If a system default
286 -- is being used then we must set to the 'current' argument value.
287 --
288 If (p_rec.start_date_active = hr_api.g_date) then
289 p_rec.start_date_active :=
290 ota_coi_shd.g_old_rec.start_date_active;
291 End If;
292 If (p_rec.end_date_active = hr_api.g_date) then
293 p_rec.end_date_active :=
294 ota_coi_shd.g_old_rec.end_date_active;
295 End If;
296 If (p_rec.primary_flag = hr_api.g_varchar2) then
297 p_rec.primary_flag :=
298 ota_coi_shd.g_old_rec.primary_flag;
299 End If;
300 --
301 End convert_defs;
302 --
303 -- ----------------------------------------------------------------------------
304 -- |---------------------------------< upd >----------------------------------|
305 -- ----------------------------------------------------------------------------
306 Procedure upd
307 (p_effective_date in date
308 ,p_rec in out nocopy ota_coi_shd.g_rec_type
309 ) is
310 --
311 l_proc varchar2(72) := g_package||'upd';
312 --
313 Begin
314 hr_utility.set_location('Entering:'||l_proc, 5);
315 --
316 -- We must lock the row which we need to update.
317 --
318 ota_coi_shd.lck
319 (p_rec.chat_id
320 ,p_rec.object_id
321 ,p_rec.object_type
322 ,p_rec.object_version_number
323 );
324 --
325 -- 1. During an update system defaults are used to determine if
326 -- arguments have been defaulted or not. We must therefore
327 -- derive the full record structure values to be updated.
328 --
329 -- 2. Call the supporting update validate operations.
330 --
331 convert_defs(p_rec);
332 ota_coi_bus.update_validate
333 (p_effective_date
334 ,p_rec
335 );
336 --
337 -- Call to raise any errors on multi-message list
338 hr_multi_message.end_validation_set;
339 --
340 -- Call the supporting pre-update operation
341 --
342 ota_coi_upd.pre_update(p_rec);
343 --
344 -- Update the row.
345 --
346 ota_coi_upd.update_dml(p_rec);
347 --
348 -- Call the supporting post-update operation
349 --
350 ota_coi_upd.post_update
351 (p_effective_date
352 ,p_rec
353 );
354 --
355 -- Call to raise any errors on multi-message list
356 hr_multi_message.end_validation_set;
357 End upd;
358 --
359 -- ----------------------------------------------------------------------------
360 -- |---------------------------------< upd >----------------------------------|
361 -- ----------------------------------------------------------------------------
362 Procedure upd
363 (p_effective_date in date
364 ,p_chat_id in number
365 ,p_object_id in number
366 ,p_object_type in varchar2
367 ,p_object_version_number in out nocopy number
368 ,p_start_date_active in date default hr_api.g_date
369 ,p_end_date_active in date default hr_api.g_date
370 ,p_primary_flag in varchar2 default hr_api.g_varchar2
371 ) is
372 --
373 l_rec ota_coi_shd.g_rec_type;
374 l_proc varchar2(72) := g_package||'upd';
375 --
376 Begin
377 hr_utility.set_location('Entering:'||l_proc, 5);
378 --
379 -- Call conversion function to turn arguments into the
380 -- l_rec structure.
381 --
382 l_rec :=
383 ota_coi_shd.convert_args
384 (p_chat_id
385 ,p_object_id
386 ,p_object_type
387 ,p_start_date_active
388 ,p_end_date_active
389 ,p_primary_flag
390 ,p_object_version_number
391 );
392 --
393 -- Having converted the arguments into the
394 -- plsql record structure we call the corresponding record
395 -- business process.
396 --
397 ota_coi_upd.upd
398 (p_effective_date
399 ,l_rec
400 );
401 p_object_version_number := l_rec.object_version_number;
402 --
403 hr_utility.set_location(' Leaving:'||l_proc, 10);
404 End upd;
405 --
406 end ota_coi_upd;
[Home] [Help]