DBA Data[Home] [Help]

PACKAGE BODY: APPS.PER_CNT_UPD

Source


1 Package Body per_cnt_upd as
2 /* $Header: pecntrhi.pkb 120.1 2005/11/03 15:07 dgarg noship $ */
3 --
4 -- ----------------------------------------------------------------------------
5 -- |                     Private Global Definitions                           |
6 -- ----------------------------------------------------------------------------
7 --
8 g_package  varchar2(33) := '  per_cnt_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_cnt_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   --
64   --
65   --
66   -- Update the per_ri_configurations_tl Row
67   --
68   update per_ri_configurations_tl
69     set
70      configuration_code              = p_rec.configuration_code
71     ,configuration_name              = p_rec.configuration_name
72     ,configuration_description       = p_rec.configuration_description
73     ,language                        = p_rec.language
74     ,source_lang                     = p_rec.source_lang
75     where configuration_code = p_rec.configuration_code
76     and language = p_rec.language;
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_cnt_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_cnt_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_cnt_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_cnt_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_cnt_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_cnt_rku.after_update
191       (p_effective_date              => p_effective_date
192       ,p_configuration_code
193       => p_rec.configuration_code
194       ,p_configuration_name
195       => p_rec.configuration_name
196       ,p_configuration_description
197       => p_rec.configuration_description
198       ,p_language
199       => p_rec.language
200       ,p_source_lang
201       => p_rec.source_lang
202       ,p_configuration_name_o
203       => per_cnt_shd.g_old_rec.configuration_name
204       ,p_configuration_description_o
205       => per_cnt_shd.g_old_rec.configuration_description
206       ,p_source_lang_o
207       => per_cnt_shd.g_old_rec.source_lang
208       );
209     --
210   exception
211     --
212     when hr_api.cannot_find_prog_unit then
213       --
214       hr_api.cannot_find_prog_unit_error
215         (p_module_name => 'PER_RI_CONFIGURATIONS_TL'
216         ,p_hook_type   => 'AU');
217       --
218   end;
219   --
220   hr_utility.set_location(' Leaving:'||l_proc, 10);
221 End post_update;
222 --
223 -- ----------------------------------------------------------------------------
224 -- |-----------------------------< convert_defs >-----------------------------|
225 -- ----------------------------------------------------------------------------
226 -- {Start Of Comments}
227 --
228 -- Description:
229 --   The Convert_Defs procedure has one very important function:
230 --   It must return the record structure for the row with all system defaulted
231 --   values converted into its corresponding parameter value for update. When
232 --   we attempt to update a row through the Upd process , certain
233 --   parameters can be defaulted which enables flexibility in the calling of
234 --   the upd process (e.g. only attributes which need to be updated need to be
235 --   specified). For the upd process to determine which attributes
236 --   have NOT been specified we need to check if the parameter has a reserved
237 --   system default value. Therefore, for all parameters which have a
238 --   corresponding reserved system default mechanism specified we need to
239 --   check if a system default is being used. If a system default is being
240 --   used then we convert the defaulted value into its corresponding attribute
241 --   value held in the g_old_rec data structure.
242 --
243 -- Prerequisites:
244 --   This private function can only be called from the upd process.
245 --
246 -- In Parameters:
247 --   A Pl/Sql record structure.
248 --
249 -- Post Success:
250 --   The record structure will be returned with all system defaulted parameter
251 --   values converted into its current row attribute value.
252 --
253 -- Post Failure:
254 --   No direct error handling is required within this function. Any possible
255 --   errors within this procedure will be a PL/SQL value error due to
256 --   conversion of datatypes or data lengths.
257 --
258 -- Developer Implementation Notes:
259 --   None.
260 --
261 -- Access Status:
262 --   Internal Row Handler Use Only.
263 --
264 -- {End Of Comments}
265 -- ----------------------------------------------------------------------------
266 Procedure convert_defs
267   (p_rec in out nocopy per_cnt_shd.g_rec_type
268   ) is
269 --
270 Begin
271   --
272   -- We must now examine each argument value in the
273   -- p_rec plsql record structure
274   -- to see if a system default is being used. If a system default
275   -- is being used then we must set to the 'current' argument value.
276   --
277   If (p_rec.configuration_name = hr_api.g_varchar2) then
278     p_rec.configuration_name :=
279     per_cnt_shd.g_old_rec.configuration_name;
280   End If;
281   If (p_rec.configuration_description = hr_api.g_varchar2) then
282     p_rec.configuration_description :=
283     per_cnt_shd.g_old_rec.configuration_description;
284   End If;
285   If (p_rec.source_lang = hr_api.g_varchar2) then
286     p_rec.source_lang :=
287     per_cnt_shd.g_old_rec.source_lang;
288   End If;
289   --
290 End convert_defs;
291 --
292 -- ----------------------------------------------------------------------------
293 -- |---------------------------------< upd >----------------------------------|
294 -- ----------------------------------------------------------------------------
295 Procedure upd
296   (p_effective_date               in date
297   ,p_rec                          in out nocopy per_cnt_shd.g_rec_type
298   ) is
299 --
300   l_proc  varchar2(72) := g_package||'upd';
301 --
302 Begin
303   hr_utility.set_location('Entering:'||l_proc, 5);
304   --
305   -- We must lock the row which we need to update.
306   --
307   per_cnt_shd.lck
308     (p_rec.configuration_code
309     ,p_rec.language
310     );
311   --
312   -- 1. During an update system defaults are used to determine if
313   --    arguments have been defaulted or not. We must therefore
314   --    derive the full record structure values to be updated.
315   --
316   -- 2. Call the supporting update validate operations.
317   --
318   convert_defs(p_rec);
319   per_cnt_bus.update_validate
320      (p_effective_date
321      ,p_rec
322      );
323   --
324   -- Call to raise any errors on multi-message list
325   hr_multi_message.end_validation_set;
326   --
327   -- Call the supporting pre-update operation
328   --
329   per_cnt_upd.pre_update(p_rec);
330   --
331   -- Update the row.
332   --
333   per_cnt_upd.update_dml(p_rec);
334   --
335   -- Call the supporting post-update operation
336   --
337   per_cnt_upd.post_update
338      (p_effective_date
339      ,p_rec
340      );
341   --
342   -- Call to raise any errors on multi-message list
343   hr_multi_message.end_validation_set;
344 End upd;
345 --
346 -- ----------------------------------------------------------------------------
347 -- |---------------------------------< upd >----------------------------------|
348 -- ----------------------------------------------------------------------------
349 Procedure upd
350   (p_effective_date               in     date
351   ,p_configuration_code           in     varchar2
352   ,p_configuration_name           in     varchar2  default hr_api.g_varchar2
353   ,p_language                     in     varchar2
354   ,p_source_lang                  in     varchar2  default hr_api.g_varchar2
355   ,p_configuration_description    in     varchar2  default hr_api.g_varchar2
356   ) is
357 --
358   l_rec   per_cnt_shd.g_rec_type;
359   l_proc  varchar2(72) := g_package||'upd';
360 --
361 Begin
362   hr_utility.set_location('Entering:'||l_proc, 5);
363   --
364   -- Call conversion function to turn arguments into the
365   -- l_rec structure.
366   --
367   l_rec :=
368   per_cnt_shd.convert_args
369   (p_configuration_code
370   ,p_configuration_name
371   ,p_configuration_description
372   ,p_language
373   ,p_source_lang
374   );
375   --
376   -- Having converted the arguments into the
377   -- plsql record structure we call the corresponding record
378   -- business process.
379   --
380   per_cnt_upd.upd
381      (p_effective_date
382      ,l_rec
383      );
384   --
385   --
386   hr_utility.set_location(' Leaving:'||l_proc, 10);
387 End upd;
388 --
389 -- ----------------------------------------------------------------------------
390 -- |------------------------------< upd_tl >----------------------------------|
391 -- ----------------------------------------------------------------------------
392 Procedure upd_tl
393   (p_effective_date               in date
394   ,p_language_code                 in varchar2
395   ,p_configuration_code           in varchar2
396   ,p_configuration_name           in varchar2 default hr_api.g_varchar2
397   ,p_configuration_description    in varchar2 default hr_api.g_varchar2
398   ) is
399   --
400   -- Cursor to obtain the translation rows where the language or
401   -- source_lang match the specified language.
402   --
403   cursor csr_upd_langs is
404     select cnt.language
405       from per_ri_configurations_tl cnt
406      where cnt.configuration_code = p_configuration_code
407        and p_language_code in (cnt.language
408                               ,cnt.source_lang);
409   --
410   l_proc  varchar2(72) := g_package||'upd_tl';
411   --
412 Begin
413   hr_utility.set_location('Entering:'||l_proc,10);
414   --
415   -- Update the translated values for every matching row
416   -- setting SOURCE_LANG to the specified language.
417   --
418   for l_lang in csr_upd_langs loop
419     per_cnt_upd.upd
420       (p_effective_date              => p_effective_date
421       ,p_configuration_code          => p_configuration_code
422       ,p_language                    => l_lang.language
423       ,p_source_lang                 => p_language_code
424       ,p_configuration_name          => p_configuration_name
425       ,p_configuration_description   => p_configuration_description
426       );
427   end loop;
428   --
429   hr_utility.set_location(' Leaving:'||l_proc,20);
430 End upd_tl;
431 --
432 end per_cnt_upd;