DBA Data[Home] [Help]

PACKAGE BODY: APPS.PER_STB_UPD

Source


1 Package Body per_stb_upd as
2 /* $Header: pestbrhi.pkb 115.0 2003/07/03 06:26:56 kavenkat noship $ */
3 --
4 -- ----------------------------------------------------------------------------
5 -- |                     Private Global Definitions                           |
6 -- ----------------------------------------------------------------------------
7 --
8 g_package  varchar2(33) := '  per_stb_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 per_stb_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 per_ri_setup_tasks Row
69   --
70   update per_ri_setup_tasks
71     set
72      setup_task_code                 = p_rec.setup_task_code
73     ,workbench_item_code             = p_rec.workbench_item_code
74     ,setup_task_sequence             = p_rec.setup_task_sequence
75     ,setup_task_status               = p_rec.setup_task_status
76     ,setup_task_creation_date        = p_rec.setup_task_creation_date
77     ,setup_task_last_modified_date   = p_rec.setup_task_last_modified_date
78     ,setup_task_type                 = p_rec.setup_task_type
79     ,setup_task_action               = p_rec.setup_task_action
80     ,object_version_number           = p_rec.object_version_number
81     where setup_task_code = p_rec.setup_task_code;
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     per_stb_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     per_stb_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     per_stb_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 per_stb_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 per_stb_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     per_stb_rku.after_update
196       (p_effective_date                => p_effective_date
197       ,p_setup_task_code               => p_rec.setup_task_code
198       ,p_workbench_item_code           => p_rec.workbench_item_code
199       ,p_setup_task_sequence           => p_rec.setup_task_sequence
200       ,p_setup_task_status             => p_rec.setup_task_status
201       ,p_setup_task_creation_date      => p_rec.setup_task_creation_date
202       ,p_setup_task_last_modified_dat  => p_rec.setup_task_last_modified_date
203       ,p_setup_task_type               => p_rec.setup_task_type
204       ,p_setup_task_action             => p_rec.setup_task_action
205       ,p_object_version_number         => p_rec.object_version_number
206       ,p_workbench_item_code_o         => per_stb_shd.g_old_rec.workbench_item_code
207       ,p_setup_task_sequence_o         => per_stb_shd.g_old_rec.setup_task_sequence
208       ,p_setup_task_status_o           => per_stb_shd.g_old_rec.setup_task_status
209       ,p_setup_task_creation_date_o    => per_stb_shd.g_old_rec.setup_task_creation_date
210       ,p_setup_task_last_modified_d_o  => per_stb_shd.g_old_rec.setup_task_last_modified_date
211       ,p_setup_task_type_o             => per_stb_shd.g_old_rec.setup_task_type
212       ,p_setup_task_action_o           => per_stb_shd.g_old_rec.setup_task_action
213       ,p_object_version_number_o       => per_stb_shd.g_old_rec.object_version_number
214       );
215     --
216   exception
217     --
218     when hr_api.cannot_find_prog_unit then
219       --
220       hr_api.cannot_find_prog_unit_error
221         (p_module_name => 'PER_RI_SETUP_TASKS'
222         ,p_hook_type   => 'AU');
223       --
224   end;
225   --
226   hr_utility.set_location(' Leaving:'||l_proc, 10);
227 End post_update;
228 --
229 -- ----------------------------------------------------------------------------
230 -- |-----------------------------< convert_defs >-----------------------------|
231 -- ----------------------------------------------------------------------------
232 -- {Start Of Comments}
233 --
234 -- Description:
235 --   The Convert_Defs procedure has one very important function:
236 --   It must return the record structure for the row with all system defaulted
237 --   values converted into its corresponding parameter value for update. When
238 --   we attempt to update a row through the Upd process , certain
239 --   parameters can be defaulted which enables flexibility in the calling of
240 --   the upd process (e.g. only attributes which need to be updated need to be
241 --   specified). For the upd process to determine which attributes
242 --   have NOT been specified we need to check if the parameter has a reserved
243 --   system default value. Therefore, for all parameters which have a
244 --   corresponding reserved system default mechanism specified we need to
245 --   check if a system default is being used. If a system default is being
246 --   used then we convert the defaulted value into its corresponding attribute
247 --   value held in the g_old_rec data structure.
248 --
249 -- Prerequisites:
250 --   This private function can only be called from the upd process.
251 --
252 -- In Parameters:
253 --   A Pl/Sql record structure.
254 --
255 -- Post Success:
256 --   The record structure will be returned with all system defaulted parameter
257 --   values converted into its current row attribute value.
258 --
259 -- Post Failure:
260 --   No direct error handling is required within this function. Any possible
261 --   errors within this procedure will be a PL/SQL value error due to
262 --   conversion of datatypes or data lengths.
263 --
264 -- Developer Implementation Notes:
265 --   None.
266 --
267 -- Access Status:
268 --   Internal Row Handler Use Only.
269 --
270 -- {End Of Comments}
271 -- ----------------------------------------------------------------------------
272 Procedure convert_defs
273   (p_rec in out nocopy per_stb_shd.g_rec_type
274   ) is
275 --
276 Begin
277   --
278   -- We must now examine each argument value in the
279   -- p_rec plsql record structure
280   -- to see if a system default is being used. If a system default
281   -- is being used then we must set to the 'current' argument value.
282   --
283   If (p_rec.workbench_item_code = hr_api.g_varchar2) then
284     p_rec.workbench_item_code :=
285     per_stb_shd.g_old_rec.workbench_item_code;
286   End If;
287   If (p_rec.setup_task_sequence = hr_api.g_number) then
288     p_rec.setup_task_sequence :=
289     per_stb_shd.g_old_rec.setup_task_sequence;
290   End If;
291   If (p_rec.setup_task_status = hr_api.g_varchar2) then
292     p_rec.setup_task_status :=
293     per_stb_shd.g_old_rec.setup_task_status;
294   End If;
295   If (p_rec.setup_task_creation_date = hr_api.g_date) then
296     p_rec.setup_task_creation_date :=
297     per_stb_shd.g_old_rec.setup_task_creation_date;
298   End If;
299   If (p_rec.setup_task_last_modified_date = hr_api.g_date) then
300     p_rec.setup_task_last_modified_date :=
301     per_stb_shd.g_old_rec.setup_task_last_modified_date;
302   End If;
303   If (p_rec.setup_task_type = hr_api.g_varchar2) then
304     p_rec.setup_task_type :=
305     per_stb_shd.g_old_rec.setup_task_type;
306   End If;
307   If (p_rec.setup_task_action = hr_api.g_varchar2) then
308     p_rec.setup_task_action :=
309     per_stb_shd.g_old_rec.setup_task_action;
310   End If;
311   --
312 End convert_defs;
313 --
314 -- ----------------------------------------------------------------------------
315 -- |---------------------------------< upd >----------------------------------|
316 -- ----------------------------------------------------------------------------
317 Procedure upd
318   (p_effective_date               in date
319   ,p_rec                          in out nocopy per_stb_shd.g_rec_type
320   ) is
321 --
322   l_proc  varchar2(72) := g_package||'upd';
323 --
324 Begin
325   hr_utility.set_location('Entering:'||l_proc, 5);
326   --
327   -- We must lock the row which we need to update.
328   --
329   per_stb_shd.lck
330     (p_rec.setup_task_code
331     ,p_rec.object_version_number
332     );
333   --
334   -- 1. During an update system defaults are used to determine if
335   --    arguments have been defaulted or not. We must therefore
336   --    derive the full record structure values to be updated.
337   --
338   -- 2. Call the supporting update validate operations.
339   --
340   convert_defs(p_rec);
341   per_stb_bus.update_validate
342      (p_effective_date
343      ,p_rec
344      );
345   --
346   -- Call to raise any errors on multi-message list
347   hr_multi_message.end_validation_set;
348   --
349   -- Call the supporting pre-update operation
350   --
351   per_stb_upd.pre_update(p_rec);
352   --
353   -- Update the row.
354   --
355   per_stb_upd.update_dml(p_rec);
356   --
357   -- Call the supporting post-update operation
358   --
359   per_stb_upd.post_update
360      (p_effective_date
361      ,p_rec
362      );
363   --
364   -- Call to raise any errors on multi-message list
365   hr_multi_message.end_validation_set;
366 End upd;
367 --
368 -- ----------------------------------------------------------------------------
369 -- |---------------------------------< upd >----------------------------------|
370 -- ----------------------------------------------------------------------------
371 Procedure upd
372   (p_effective_date               in     date
373   ,p_setup_task_code              in     varchar2
374   ,p_object_version_number        in out nocopy number
375   ,p_workbench_item_code          in     varchar2  default hr_api.g_varchar2
376   ,p_setup_task_sequence          in     number    default hr_api.g_number
377   ,p_setup_task_status            in     varchar2  default hr_api.g_varchar2
378   ,p_setup_task_creation_date     in     date      default hr_api.g_date
379   ,p_setup_task_last_modified_dat in     date      default hr_api.g_date
380   ,p_setup_task_type              in     varchar2  default hr_api.g_varchar2
381   ,p_setup_task_action            in     varchar2  default hr_api.g_varchar2
382   ) is
383 --
384   l_rec   per_stb_shd.g_rec_type;
385   l_proc  varchar2(72) := g_package||'upd';
386 --
387 Begin
388   hr_utility.set_location('Entering:'||l_proc, 5);
389   --
390   -- Call conversion function to turn arguments into the
391   -- l_rec structure.
392   --
393   l_rec :=
394   per_stb_shd.convert_args
395   (p_setup_task_code
396   ,p_workbench_item_code
397   ,p_setup_task_sequence
398   ,p_setup_task_status
399   ,p_setup_task_creation_date
400   ,p_setup_task_last_modified_dat
401   ,p_setup_task_type
402   ,p_setup_task_action
403   ,p_object_version_number
404   );
405   --
406   -- Having converted the arguments into the
407   -- plsql record structure we call the corresponding record
408   -- business process.
409   --
410   per_stb_upd.upd
411      (p_effective_date
412      ,l_rec
413      );
414   p_object_version_number := l_rec.object_version_number;
415   --
416   hr_utility.set_location(' Leaving:'||l_proc, 10);
417 End upd;
418 --
419 end per_stb_upd;