DBA Data[Home] [Help]

PACKAGE BODY: APPS.PER_CNF_UPD

Source


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