DBA Data[Home] [Help]

PACKAGE BODY: APPS.HR_ITL_UPD

Source


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