DBA Data[Home] [Help]

PACKAGE BODY: APPS.IRC_IVC_UPD

Source


1 Package Body irc_ivc_upd as
2 /* $Header: irivcrhi.pkb 120.0 2005/07/26 15:12:26 mbocutt noship $ */
3 --
4 -- ----------------------------------------------------------------------------
5 -- |                     Private Global Definitions                           |
6 -- ----------------------------------------------------------------------------
7 --
8 g_package  varchar2(33) := '  irc_ivc_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_ivc_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_vacancy_considerations Row
69   --
70   update irc_vacancy_considerations
71     set
72      party_id                        = p_rec.party_id
73     ,consideration_status            = p_rec.consideration_status
74     ,object_version_number           = p_rec.object_version_number
75     where  vacancy_consideration_id = p_rec.vacancy_consideration_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_ivc_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_ivc_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_ivc_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_ivc_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_ivc_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_ivc_rku.after_update
190       (p_effective_date              => p_effective_date
191       ,p_vacancy_consideration_id =>p_rec.vacancy_consideration_id
192       ,p_person_id=>p_rec.person_id
193       ,p_party_id
194       => p_rec.party_id
195       ,p_vacancy_id
196       => p_rec.vacancy_id
197       ,p_consideration_status
198       => p_rec.consideration_status
199       ,p_object_version_number
200       => p_rec.object_version_number
201       ,p_consideration_status_o
202       => irc_ivc_shd.g_old_rec.consideration_status
203       ,p_object_version_number_o
204       => irc_ivc_shd.g_old_rec.object_version_number
205       );
206     --
207   exception
208     --
209     when hr_api.cannot_find_prog_unit then
210       --
211       hr_api.cannot_find_prog_unit_error
212         (p_module_name => 'IRC_VACANCY_CONSIDERATIONS'
213         ,p_hook_type   => 'AU');
214       --
215   end;
216   --
217   hr_utility.set_location(' Leaving:'||l_proc, 10);
218 End post_update;
219 --
220 -- ----------------------------------------------------------------------------
221 -- |-----------------------------< convert_defs >-----------------------------|
222 -- ----------------------------------------------------------------------------
223 -- {Start Of Comments}
224 --
225 -- Description:
226 --   The Convert_Defs procedure has one very important function:
227 --   It must return the record structure for the row with all system defaulted
228 --   values converted into its corresponding parameter value for update. When
229 --   we attempt to update a row through the Upd process , certain
230 --   parameters can be defaulted which enables flexibility in the calling of
231 --   the upd process (e.g. only attributes which need to be updated need to be
232 --   specified). For the upd process to determine which attributes
233 --   have NOT been specified we need to check if the parameter has a reserved
234 --   system default value. Therefore, for all parameters which have a
235 --   corresponding reserved system default mechanism specified we need to
236 --   check if a system default is being used. If a system default is being
237 --   used then we convert the defaulted value into its corresponding attribute
238 --   value held in the g_old_rec data structure.
239 --
240 -- Prerequisites:
241 --   This private function can only be called from the upd process.
242 --
243 -- In Parameters:
244 --   A Pl/Sql record structure.
245 --
246 -- Post Success:
247 --   The record structure will be returned with all system defaulted parameter
248 --   values converted into its current row attribute value.
249 --
250 -- Post Failure:
251 --   No direct error handling is required within this function. Any possible
252 --   errors within this procedure will be a PL/SQL value error due to
253 --   conversion of datatypes or data lengths.
254 --
255 -- Developer Implementation Notes:
256 --   None.
257 --
258 -- Access Status:
259 --   Internal Row Handler Use Only.
260 --
261 -- {End Of Comments}
262 -- ----------------------------------------------------------------------------
263 Procedure convert_defs
264   (p_rec in out nocopy irc_ivc_shd.g_rec_type
265   ) is
266 --
267 Begin
268   --
269   -- We must now examine each argument value in the
270   -- p_rec plsql record structure
271   -- to see if a system default is being used. If a system default
272   -- is being used then we must set to the 'current' argument value.
273   --
274   If (p_rec.consideration_status = hr_api.g_varchar2) then
275     p_rec.consideration_status :=
276     irc_ivc_shd.g_old_rec.consideration_status;
277   End If;
278   If (p_rec.party_id = hr_api.g_number) then
279     p_rec.party_id :=
280     irc_ivc_shd.g_old_rec.party_id;
281   End If;
282   --
283 End convert_defs;
284 --
285 -- ----------------------------------------------------------------------------
286 -- |---------------------------------< upd >----------------------------------|
287 -- ----------------------------------------------------------------------------
288 Procedure upd
289   (p_effective_date               in date
290   ,p_rec                          in out nocopy irc_ivc_shd.g_rec_type
291   ) is
292 --
293   l_proc  varchar2(72) := g_package||'upd';
294 --
295 Begin
296   hr_utility.set_location('Entering:'||l_proc, 5);
297   --
298   -- We must lock the row which we need to update.
299   --
300   irc_ivc_shd.lck
301     (p_rec.vacancy_consideration_id
302     ,p_rec.object_version_number
303     );
304   --
305   -- 1. During an update system defaults are used to determine if
306   --    arguments have been defaulted or not. We must therefore
307   --    derive the full record structure values to be updated.
308   --
309   -- 2. Call the supporting update validate operations.
310   --
311   convert_defs(p_rec);
312   irc_ivc_bus.update_validate
313      (p_effective_date
314      ,p_rec
315      );
316   --
317    -- Call to raise any errors on multi-message list
318   hr_multi_message.end_validation_set;
319   -- Call the supporting pre-update operation
320   --
321   irc_ivc_upd.pre_update(p_rec);
322   --
323   if p_rec.person_id is null then
324     p_rec.person_id:=irc_ivc_shd.g_old_rec.person_id;
325   end if;
326   if p_rec.vacancy_id is null then
327     p_rec.vacancy_id:=irc_ivc_shd.g_old_rec.vacancy_id;
328   end if;
329   -- Update the row.
330   --
331   irc_ivc_upd.update_dml(p_rec);
332   --
333   -- Call the supporting post-update operation
334   --
335   irc_ivc_upd.post_update
336      (p_effective_date
337      ,p_rec
338      );
339   --
340   -- Call to raise any errors on multi-message list
341   hr_multi_message.end_validation_set;
342 End upd;
343 --
344 -- ----------------------------------------------------------------------------
345 -- |---------------------------------< upd >----------------------------------|
346 -- ----------------------------------------------------------------------------
347 Procedure upd
348   (p_effective_date               in     date
349   ,p_vacancy_consideration_id     in     number
350   ,p_party_id                     in     number    default hr_api.g_number
351   ,p_object_version_number        in out nocopy number
352   ,p_consideration_status         in     varchar2  default hr_api.g_varchar2
353   ) is
354 --
355   l_rec   irc_ivc_shd.g_rec_type;
356   l_proc  varchar2(72) := g_package||'upd';
357 --
358 Begin
359   hr_utility.set_location('Entering:'||l_proc, 5);
360   --
361   -- Call conversion function to turn arguments into the
362   -- l_rec structure.
363   --
364   l_rec :=
365   irc_ivc_shd.convert_args
366   (p_vacancy_consideration_id
367   ,null
368   ,p_party_id
369   ,null
370   ,p_consideration_status
371   ,p_object_version_number
372   );
373   --
374   -- Having converted the arguments into the
375   -- plsql record structure we call the corresponding record
376   -- business process.
377   --
378   irc_ivc_upd.upd
379      (p_effective_date
380      ,l_rec
381      );
382   p_object_version_number := l_rec.object_version_number;
383   --
384   hr_utility.set_location(' Leaving:'||l_proc, 10);
385 End upd;
386 --
387 end irc_ivc_upd;