DBA Data[Home] [Help]

PACKAGE BODY: APPS.GHR_CBA_UPD

Source


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