DBA Data[Home] [Help]

PACKAGE BODY: APPS.PQP_DET_DEL

Source


1 Package Body pqp_det_del as
2 /* $Header: pqdetrhi.pkb 115.8 2003/02/17 22:14:03 tmehra ship $ */
3 --
4 -- ----------------------------------------------------------------------------
5 -- |                     Private Global Definitions                           |
6 -- ----------------------------------------------------------------------------
7 --
8 g_package  varchar2(33)	:= '  pqp_det_del.';  -- Global package name
9 --
10 -- ----------------------------------------------------------------------------
11 -- |------------------------------< delete_dml >------------------------------|
12 -- ----------------------------------------------------------------------------
13 -- {Start Of Comments}
14 --
15 -- Description:
16 --   This procedure controls the actual dml delete logic. The functions of
17 --   this procedure are as follows:
18 --   1) To set and unset the g_api_dml status as required (as we are about to
19 --      perform dml).
20 --   2) To delete the specified row from the schema using the primary key in
21 --      the predicates.
22 --   3) To trap any constraint violations that may have occurred.
23 --   4) To raise any other errors.
24 --
25 -- Prerequisites:
26 --   This is an internal private procedure which must be called from the del
27 --   procedure.
28 --
29 -- In Parameters:
30 --   A Pl/Sql record structre.
31 --
32 -- Post Success:
33 --   The specified row will be delete from the schema.
34 --
35 -- Post Failure:
36 --   On the delete dml failure it is important to note that we always reset the
37 --   g_api_dml status to false.
38 --   If a child integrity constraint violation is raised the
39 --   constraint_error procedure will be called.
40 --   If any other error is reported, the error will be raised after the
41 --   g_api_dml status is reset.
42 --
43 -- Developer Implementation Notes:
44 --   None.
45 --
46 -- Access Status:
47 --   Internal Row Handler Use Only.
48 --
49 -- {End Of Comments}
50 -- ----------------------------------------------------------------------------
51 Procedure delete_dml(p_rec in pqp_det_shd.g_rec_type) is
52 --
53   l_proc  varchar2(72) := g_package||'delete_dml';
54 --
55 Begin
56   hr_utility.set_location('Entering:'||l_proc, 5);
57   --
58   pqp_det_shd.g_api_dml := true;  -- Set the api dml status
59   --
60   -- Delete the pqp_analyzed_alien_details row.
61   --
62   delete from pqp_analyzed_alien_details
63   where analyzed_data_details_id = p_rec.analyzed_data_details_id;
64   --
65   pqp_det_shd.g_api_dml := false;   -- Unset the api dml status
66   --
67   hr_utility.set_location(' Leaving:'||l_proc, 10);
68 --
69 Exception
70   When hr_api.child_integrity_violated then
71     -- Child integrity has been violated
72     pqp_det_shd.g_api_dml := false;   -- Unset the api dml status
73     pqp_det_shd.constraint_error
74       (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
75   When Others Then
76     pqp_det_shd.g_api_dml := false;   -- Unset the api dml status
77     Raise;
78 End delete_dml;
79 --
80 -- ----------------------------------------------------------------------------
81 -- |------------------------------< pre_delete >------------------------------|
82 -- ----------------------------------------------------------------------------
83 -- {Start Of Comments}
84 --
85 -- Description:
86 --   This private procedure contains any processing which is required before
87 --   the delete dml.
88 --
89 -- Prerequisites:
90 --   This is an internal procedure which is called from the del procedure.
91 --
92 -- In Parameters:
93 --   A Pl/Sql record structre.
94 --
95 -- Post Success:
96 --   Processing continues.
97 --
98 -- Post Failure:
99 --   If an error has occurred, an error message and exception will be raised
100 --   but not handled.
101 --
102 -- Developer Implementation Notes:
103 --   Any pre-processing required before the delete dml is issued should be
104 --   coded within this procedure. It is important to note that any 3rd party
105 --   maintenance should be reviewed before placing in this procedure.
106 --
107 -- Access Status:
108 --   Internal Row Handler Use Only.
109 --
110 -- {End Of Comments}
111 -- ----------------------------------------------------------------------------
112 Procedure pre_delete(p_rec in pqp_det_shd.g_rec_type) is
113 --
114   l_proc  varchar2(72) := g_package||'pre_delete';
115 --
116 Begin
117   hr_utility.set_location('Entering:'||l_proc, 5);
118   --
119   hr_utility.set_location(' Leaving:'||l_proc, 10);
120 End pre_delete;
121 --
122 -- ----------------------------------------------------------------------------
123 -- |-----------------------------< post_delete >------------------------------|
124 -- ----------------------------------------------------------------------------
125 -- {Start Of Comments}
126 --
127 -- Description:
128 --   This private procedure contains any processing which is required after the
129 --   delete dml.
130 --
131 -- Prerequisites:
132 --   This is an internal procedure which is called from the del procedure.
133 --
134 -- In Parameters:
135 --   A Pl/Sql record structre.
136 --
137 -- Post Success:
138 --   Processing continues.
139 --
140 -- Post Failure:
141 --   If an error has occurred, an error message and exception will be raised
142 --   but not handled.
143 --
144 -- Developer Implementation Notes:
145 --   Any post-processing required after the delete dml is issued should be
146 --   coded within this procedure. It is important to note that any 3rd party
147 --   maintenance should be reviewed before placing in this procedure.
148 --
149 -- Access Status:
150 --   Internal table Handler Use Only.
151 --
152 -- {End Of Comments}
153 -- ----------------------------------------------------------------------------
154 Procedure post_delete(
155 p_effective_date in date,p_rec in pqp_det_shd.g_rec_type) is
156 --
157   l_proc  varchar2(72) := g_package||'post_delete';
158 --
159 Begin
160   hr_utility.set_location('Entering:'||l_proc, 5);
161 --
162   --
163   -- Start of API User Hook for post_delete.
164   --
165   begin
166     --
167     pqp_det_rkd.after_delete
168       (
169   p_analyzed_data_details_id      =>p_rec.analyzed_data_details_id
170  ,p_analyzed_data_id_o            =>pqp_det_shd.g_old_rec.analyzed_data_id
171  ,p_income_code_o                 =>pqp_det_shd.g_old_rec.income_code
172  ,p_withholding_rate_o            =>pqp_det_shd.g_old_rec.withholding_rate
173  ,p_income_code_sub_type_o        =>pqp_det_shd.g_old_rec.income_code_sub_type
174  ,p_exemption_code_o              =>pqp_det_shd.g_old_rec.exemption_code
175  ,p_maximum_benefit_amount_o      =>pqp_det_shd.g_old_rec.maximum_benefit_amount
176  ,p_retro_lose_ben_amt_flag_o     =>pqp_det_shd.g_old_rec.retro_lose_ben_amt_flag
177  ,p_date_benefit_ends_o           =>pqp_det_shd.g_old_rec.date_benefit_ends
178  ,p_retro_lose_ben_date_flag_o    =>pqp_det_shd.g_old_rec.retro_lose_ben_date_flag
179  ,p_nra_exempt_from_ss_o          =>pqp_det_shd.g_old_rec.nra_exempt_from_ss
180  ,p_nra_exempt_from_medicare_o    =>pqp_det_shd.g_old_rec.nra_exempt_from_medicare
181  ,p_student_exempt_from_ss_o      =>pqp_det_shd.g_old_rec.student_exempt_from_ss
182  ,p_student_exempt_from_medi_o    =>pqp_det_shd.g_old_rec.student_exempt_from_medicare
183  ,p_addl_withholding_flag_o       =>pqp_det_shd.g_old_rec.addl_withholding_flag
184  ,p_constant_addl_tax_o           =>pqp_det_shd.g_old_rec.constant_addl_tax
185  ,p_addl_withholding_amt_o        =>pqp_det_shd.g_old_rec.addl_withholding_amt
186  ,p_addl_wthldng_amt_period_ty_o  =>pqp_det_shd.g_old_rec.addl_wthldng_amt_period_type
187  ,p_personal_exemption_o          =>pqp_det_shd.g_old_rec.personal_exemption
188  ,p_addl_exemption_allowed_o      =>pqp_det_shd.g_old_rec.addl_exemption_allowed
189  ,p_treaty_ben_allowed_flag_o     =>pqp_det_shd.g_old_rec.treaty_ben_allowed_flag
190  ,p_treaty_benefits_start_date_o  =>pqp_det_shd.g_old_rec.treaty_benefits_start_date
191  ,p_object_version_number_o       =>pqp_det_shd.g_old_rec.object_version_number
192  ,p_retro_loss_notif_sent_o       =>pqp_det_shd.g_old_rec.retro_loss_notification_sent
193  ,p_current_analysis_o            =>pqp_det_shd.g_old_rec.current_analysis
194  ,p_forecast_income_code_o        =>pqp_det_shd.g_old_rec.forecast_income_code
195       );
196     --
197   exception
198     --
199     when hr_api.cannot_find_prog_unit then
200       --
201       hr_api.cannot_find_prog_unit_error
202         (p_module_name => 'PQP_ANALYZED_ALIEN_DET'
203         ,p_hook_type   => 'AD');
204       --
205   end;
206   --
207   -- End of API User Hook for post_delete.
208   --
209   --
210   hr_utility.set_location(' Leaving:'||l_proc, 10);
211 End post_delete;
212 --
213 -- ----------------------------------------------------------------------------
214 -- |---------------------------------< del >----------------------------------|
215 -- ----------------------------------------------------------------------------
216 Procedure del
217   (
218   p_effective_date in date,
219   p_rec	      in pqp_det_shd.g_rec_type
220   ) is
221 --
222   l_proc  varchar2(72) := g_package||'del';
223 --
224 Begin
225   hr_utility.set_location('Entering:'||l_proc, 5);
226   --
227   -- We must lock the row which we need to delete.
228   --
229   pqp_det_shd.lck
230 	(
231 	p_rec.analyzed_data_details_id,
232 	p_rec.object_version_number
233 	);
234   --
235   -- Call the supporting delete validate operation
236   --
237   pqp_det_bus.delete_validate(p_rec
238   ,p_effective_date);
239   --
240   -- Call the supporting pre-delete operation
241   --
242   pre_delete(p_rec);
243   --
244   -- Delete the row.
245   --
246   delete_dml(p_rec);
247   --
248   -- Call the supporting post-delete operation
249   --
250   post_delete(
251 p_effective_date,p_rec);
252 End del;
253 --
254 -- ----------------------------------------------------------------------------
255 -- |---------------------------------< del >----------------------------------|
256 -- ----------------------------------------------------------------------------
257 Procedure del
258   (
259   p_effective_date in date,
260   p_analyzed_data_details_id           in number,
261   p_object_version_number              in number
262   ) is
263 --
264   l_rec	  pqp_det_shd.g_rec_type;
265   l_proc  varchar2(72) := g_package||'del';
266 --
267 Begin
268   hr_utility.set_location('Entering:'||l_proc, 5);
269   --
270   -- As the delete procedure accepts a plsql record structure we do need to
271   -- convert the  arguments into the record structure.
272   -- We don't need to call the supplied conversion argument routine as we
273   -- only need a few attributes.
274   --
275   l_rec.analyzed_data_details_id:= p_analyzed_data_details_id;
279   -- plsql record structure we must call the corresponding entity
276   l_rec.object_version_number := p_object_version_number;
277   --
278   -- Having converted the arguments into the det_rec
280   -- business process
281   --
282   del(
283     p_effective_date,l_rec);
284   --
285   hr_utility.set_location(' Leaving:'||l_proc, 10);
286 End del;
287 --
288 end pqp_det_del;