DBA Data[Home] [Help]

PACKAGE BODY: APPS.PQP_AAD_DEL

Source


1 Package Body pqp_aad_del as
2 /* $Header: pqaadrhi.pkb 115.5 2003/02/17 22:13:35 tmehra ship $ */
3 --
4 -- ----------------------------------------------------------------------------
5 -- |                     Private Global Definitions                           |
6 -- ----------------------------------------------------------------------------
7 --
8 g_package  varchar2(33)	:= '  pqp_aad_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_aad_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_aad_shd.g_api_dml := true;  -- Set the api dml status
59   --
60   -- Delete the pqp_analyzed_alien_data row.
61   --
62   delete from pqp_analyzed_alien_data
63   where analyzed_data_id = p_rec.analyzed_data_id;
64   --
65   pqp_aad_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_aad_shd.g_api_dml := false;   -- Unset the api dml status
73     pqp_aad_shd.constraint_error
74       (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
75   When Others Then
76     pqp_aad_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_aad_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_aad_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_aad_rkd.after_delete
168       (
169   p_analyzed_data_id              =>p_rec.analyzed_data_id
170  ,p_assignment_id_o               =>pqp_aad_shd.g_old_rec.assignment_id
171  ,p_data_source_o                 =>pqp_aad_shd.g_old_rec.data_source
172  ,p_tax_year_o                    =>pqp_aad_shd.g_old_rec.tax_year
173  ,p_current_residency_status_o    =>pqp_aad_shd.g_old_rec.current_residency_status
174  ,p_nra_to_ra_date_o              =>pqp_aad_shd.g_old_rec.nra_to_ra_date
175  ,p_target_departure_date_o       =>pqp_aad_shd.g_old_rec.target_departure_date
176  ,p_tax_residence_country_code_o  =>pqp_aad_shd.g_old_rec.tax_residence_country_code
177  ,p_treaty_info_update_date_o     =>pqp_aad_shd.g_old_rec.treaty_info_update_date
178  ,p_number_of_days_in_usa_o       =>pqp_aad_shd.g_old_rec.number_of_days_in_usa
179  ,p_withldg_allow_eligible_fla_o =>pqp_aad_shd.g_old_rec.withldg_allow_eligible_flag
180  ,p_ra_effective_date_o           =>pqp_aad_shd.g_old_rec.ra_effective_date
181  ,p_record_source_o               =>pqp_aad_shd.g_old_rec.record_source
182  ,p_visa_type_o                   =>pqp_aad_shd.g_old_rec.visa_type
183  ,p_j_sub_type_o                  =>pqp_aad_shd.g_old_rec.j_sub_type
184  ,p_primary_activity_o            =>pqp_aad_shd.g_old_rec.primary_activity
185  ,p_non_us_country_code_o         =>pqp_aad_shd.g_old_rec.non_us_country_code
186  ,p_citizenship_country_code_o    =>pqp_aad_shd.g_old_rec.citizenship_country_code
187  ,p_object_version_number_o       =>pqp_aad_shd.g_old_rec.object_version_number
188 ,p_date_8233_signed_o             =>pqp_aad_shd.g_old_rec.date_8233_signed
189 ,p_date_w4_signed_o               =>pqp_aad_shd.g_old_rec.date_w4_signed
190       );
191     --
192   exception
193     --
194     when hr_api.cannot_find_prog_unit then
195       --
196       hr_api.cannot_find_prog_unit_error
197         (p_module_name => 'PQP_ANALYZED_ALIEN_DATA'
198         ,p_hook_type   => 'AD');
199       --
200   end;
201   --
202   -- End of API User Hook for post_delete.
203   --
204   --
205   hr_utility.set_location(' Leaving:'||l_proc, 10);
206 End post_delete;
207 --
208 -- ----------------------------------------------------------------------------
209 -- |---------------------------------< del >----------------------------------|
210 -- ----------------------------------------------------------------------------
211 Procedure del
212   (
213   p_effective_date in date,
214   p_rec	      in pqp_aad_shd.g_rec_type
215   ) is
216 --
217   l_proc  varchar2(72) := g_package||'del';
218 --
219 Begin
220   hr_utility.set_location('Entering:'||l_proc, 5);
221   --
222   -- We must lock the row which we need to delete.
223   --
224   pqp_aad_shd.lck
225 	(
226 	p_rec.analyzed_data_id,
227 	p_rec.object_version_number
228 	);
229   --
230   -- Call the supporting delete validate operation
231   --
232   pqp_aad_bus.delete_validate(p_rec
233   ,p_effective_date);
234   --
235   -- Call the supporting pre-delete operation
236   --
237   pre_delete(p_rec);
238   --
239   -- Delete the row.
240   --
241   delete_dml(p_rec);
242   --
243   -- Call the supporting post-delete operation
244   --
245   post_delete(
246 p_effective_date,p_rec);
247 End del;
248 --
249 -- ----------------------------------------------------------------------------
250 -- |---------------------------------< del >----------------------------------|
251 -- ----------------------------------------------------------------------------
252 Procedure del
253   (
254   p_effective_date in date,
255   p_analyzed_data_id                   in number,
256   p_object_version_number              in number
257   ) is
258 --
259   l_rec	  pqp_aad_shd.g_rec_type;
260   l_proc  varchar2(72) := g_package||'del';
261 --
262 Begin
263   hr_utility.set_location('Entering:'||l_proc, 5);
264   --
265   -- As the delete procedure accepts a plsql record structure we do need to
266   -- convert the  arguments into the record structure.
267   -- We don't need to call the supplied conversion argument routine as we
268   -- only need a few attributes.
269   --
270   l_rec.analyzed_data_id:= p_analyzed_data_id;
271   l_rec.object_version_number := p_object_version_number;
272   --
273   -- Having converted the arguments into the analyzed_alien_data_rec
274   -- plsql record structure we must call the corresponding entity
275   -- business process
276   --
277   del(
278     p_effective_date,l_rec);
279   --
280   hr_utility.set_location(' Leaving:'||l_proc, 10);
281 End del;
282 --
283 end pqp_aad_del;