DBA Data[Home] [Help]

PACKAGE BODY: APPS.HR_FDG_UPD

Source


1 Package Body hr_fdg_upd as
2 /* $Header: hrfdgrhi.pkb 115.4 2002/12/03 10:53:27 hjonnala noship $ */
3 --
4 -- ----------------------------------------------------------------------------
5 -- |                     Private Global Definitions                           |
6 -- ----------------------------------------------------------------------------
7 --
8 g_package  varchar2(33)	:= '  hr_fdg_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_fdg_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 hr_form_data_groups_b Row
69   --
70   update hr_form_data_groups_b
71     set
72      form_data_group_id              = p_rec.form_data_group_id
73     ,object_version_number           = p_rec.object_version_number
74     ,application_id                  = p_rec.application_id
75     ,form_id                         = p_rec.form_id
76     ,data_group_name                 = p_rec.data_group_name
77     where form_data_group_id = p_rec.form_data_group_id;
78   --
79   --
80   --
81   hr_utility.set_location(' Leaving:'||l_proc, 10);
82 --
83 Exception
84   When hr_api.check_integrity_violated Then
85     -- A check constraint has been violated
86     --
87     hr_fdg_shd.constraint_error
88       (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
89   When hr_api.parent_integrity_violated Then
90     -- Parent integrity has been violated
91     --
92     hr_fdg_shd.constraint_error
93       (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
94   When hr_api.unique_integrity_violated Then
95     -- Unique integrity has been violated
96     --
97     hr_fdg_shd.constraint_error
98       (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
99   When Others Then
100     --
101     Raise;
102 End update_dml;
103 --
104 -- ----------------------------------------------------------------------------
105 -- |------------------------------< pre_update >------------------------------|
106 -- ----------------------------------------------------------------------------
107 -- {Start Of Comments}
108 --
109 -- Description:
110 --   This private procedure contains any processing which is required before
111 --   the update dml.
112 --
113 -- Prerequisites:
114 --   This is an internal procedure which is called from the upd procedure.
115 --
116 -- In Parameters:
117 --   A Pl/Sql record structure.
118 --
119 -- Post Success:
120 --   Processing continues.
121 --
122 -- Post Failure:
123 --   If an error has occurred, an error message and exception wil be raised
124 --   but not handled.
125 --
126 -- Developer Implementation Notes:
127 --   Any pre-processing required before the update dml is issued should be
128 --   coded within this procedure. It is important to note that any 3rd party
129 --   maintenance should be reviewed before placing in this procedure.
130 --
131 -- Access Status:
132 --   Internal Row Handler Use Only.
133 --
134 -- {End Of Comments}
135 -- ----------------------------------------------------------------------------
136 Procedure pre_update
137   (p_rec in hr_fdg_shd.g_rec_type
138   ) is
139 --
140   l_proc  varchar2(72) := g_package||'pre_update';
141 --
142 Begin
143   hr_utility.set_location('Entering:'||l_proc, 5);
144   --
145   hr_utility.set_location(' Leaving:'||l_proc, 10);
146 End pre_update;
147 --
148 -- ----------------------------------------------------------------------------
149 -- |-----------------------------< post_update >------------------------------|
150 -- ----------------------------------------------------------------------------
151 -- {Start Of Comments}
152 --
153 -- Description:
154 --   This private procedure contains any processing which is required after the
155 --   update dml.
156 --
157 -- Prerequisites:
158 --   This is an internal procedure which is called from the upd procedure.
159 --
160 -- In Parameters:
161 --   A Pl/Sql record structure.
162 --
163 -- Post Success:
164 --   Processing continues.
165 --
166 -- Post Failure:
167 --   If an error has occurred, an error message and exception will be raised
168 --   but not handled.
169 --
170 -- Developer Implementation Notes:
171 --   Any post-processing required after the update dml is issued should be
172 --   coded within this procedure. It is important to note that any 3rd party
173 --   maintenance should be reviewed before placing in this procedure.
174 --
175 -- Access Status:
176 --   Internal Row Handler Use Only.
177 --
178 -- {End Of Comments}
179 -- ----------------------------------------------------------------------------
180 Procedure post_update
181   (p_rec                          in hr_fdg_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     hr_fdg_rku.after_update
191       (p_form_data_group_id
192       => p_rec.form_data_group_id
193       ,p_object_version_number
194       => p_rec.object_version_number
195       ,p_application_id
196       => p_rec.application_id
197       ,p_form_id
198       => p_rec.form_id
199       ,p_data_group_name
200       => p_rec.data_group_name
201       ,p_object_version_number_o
202       => hr_fdg_shd.g_old_rec.object_version_number
203       ,p_application_id_o
204       => hr_fdg_shd.g_old_rec.application_id
205       ,p_form_id_o
206       => hr_fdg_shd.g_old_rec.form_id
207       ,p_data_group_name_o
208       => hr_fdg_shd.g_old_rec.data_group_name
209       );
210     --
211   exception
212     --
213     when hr_api.cannot_find_prog_unit then
214       --
215       hr_api.cannot_find_prog_unit_error
216         (p_module_name => 'HR_FORM_DATA_GROUPS_B'
217         ,p_hook_type   => 'AU');
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_fdg_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.application_id = hr_api.g_number) then
279     p_rec.application_id :=
280     hr_fdg_shd.g_old_rec.application_id;
281   End If;
282   If (p_rec.form_id = hr_api.g_number) then
283     p_rec.form_id :=
284     hr_fdg_shd.g_old_rec.form_id;
285   End If;
286   If (p_rec.data_group_name = hr_api.g_varchar2) then
287     p_rec.data_group_name :=
288     hr_fdg_shd.g_old_rec.data_group_name;
289   End If;
290   --
291 End convert_defs;
292 --
293 -- ----------------------------------------------------------------------------
294 -- |---------------------------------< upd >----------------------------------|
295 -- ----------------------------------------------------------------------------
296 Procedure upd
297   (p_rec                          in out nocopy hr_fdg_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_fdg_shd.lck
308     (p_rec.form_data_group_id
309     ,p_rec.object_version_number
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_fdg_bus.update_validate
320      (p_rec
321      );
322   --
323   -- Call the supporting pre-update operation
324   --
325   hr_fdg_upd.pre_update(p_rec);
326   --
327   -- Update the row.
328   --
329   hr_fdg_upd.update_dml(p_rec);
330   --
331   -- Call the supporting post-update operation
332   --
333   hr_fdg_upd.post_update
334      (p_rec
335      );
336 End upd;
337 --
338 -- ----------------------------------------------------------------------------
339 -- |---------------------------------< upd >----------------------------------|
340 -- ----------------------------------------------------------------------------
341 Procedure upd
342   (p_form_data_group_id           in     number
343   ,p_object_version_number        in out nocopy number
344   ,p_application_id               in     number    default hr_api.g_number
345   ,p_form_id                      in     number    default hr_api.g_number
346   ,p_data_group_name              in     varchar2  default hr_api.g_varchar2
347   ) is
348 --
349   l_rec	  hr_fdg_shd.g_rec_type;
350   l_proc  varchar2(72) := g_package||'upd';
351 --
352 Begin
353   hr_utility.set_location('Entering:'||l_proc, 5);
354   --
355   -- Call conversion function to turn arguments into the
356   -- l_rec structure.
357   --
358   l_rec :=
359   hr_fdg_shd.convert_args
360   (p_form_data_group_id
361   ,p_object_version_number
362   ,p_application_id
363   ,p_form_id
364   ,p_data_group_name
365   );
366   --
367   -- Having converted the arguments into the
368   -- plsql record structure we call the corresponding record
369   -- business process.
370   --
371   hr_fdg_upd.upd
372      (l_rec
373      );
374   p_object_version_number := l_rec.object_version_number;
375   --
376   hr_utility.set_location(' Leaving:'||l_proc, 10);
377 End upd;
378 --
379 end hr_fdg_upd;