DBA Data[Home] [Help]

PACKAGE BODY: APPS.IRC_APS_UPD

Source


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