DBA Data[Home] [Help]

PACKAGE BODY: APPS.PQP_GDS_DEL

Source


1 Package Body pqp_gds_del as
2 /* $Header: pqgdsrhi.pkb 120.0 2005/10/28 07:32 rvishwan noship $ */
3 --
4 -- ----------------------------------------------------------------------------
5 -- |                     Private Global Definitions                           |
6 -- ----------------------------------------------------------------------------
7 --
8 g_package  varchar2(33) := '  pqp_gds_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
52   (p_rec in pqp_gds_shd.g_rec_type
53   ) is
54 --
55   l_proc  varchar2(72) := g_package||'delete_dml';
56 --
57 Begin
58   hr_utility.set_location('Entering:'||l_proc, 5);
59   --
60   pqp_gds_shd.g_api_dml := true;  -- Set the api dml status
61   --
62   -- Delete the pqp_gap_duration_summary row.
63   --
64   delete from pqp_gap_duration_summary
65   where gap_duration_summary_id = p_rec.gap_duration_summary_id;
66   --
67   pqp_gds_shd.g_api_dml := false;   -- Unset the api dml status
68   --
69   hr_utility.set_location(' Leaving:'||l_proc, 10);
70 --
71 Exception
72   When hr_api.child_integrity_violated then
73     -- Child integrity has been violated
74     pqp_gds_shd.g_api_dml := false;   -- Unset the api dml status
75     pqp_gds_shd.constraint_error
76       (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
77   When Others Then
78     pqp_gds_shd.g_api_dml := false;   -- Unset the api dml status
79     Raise;
80 End delete_dml;
81 --
82 -- ----------------------------------------------------------------------------
83 -- |------------------------------< pre_delete >------------------------------|
84 -- ----------------------------------------------------------------------------
85 -- {Start Of Comments}
86 --
87 -- Description:
88 --   This private procedure contains any processing which is required before
89 --   the delete dml.
90 --
91 -- Prerequisites:
92 --   This is an internal procedure which is called from the del procedure.
93 --
94 -- In Parameters:
95 --   A Pl/Sql record structre.
96 --
97 -- Post Success:
98 --   Processing continues.
99 --
100 -- Post Failure:
101 --   If an error has occurred, an error message and exception will be raised
102 --   but not handled.
103 --
104 -- Developer Implementation Notes:
105 --   Any pre-processing required before the delete dml is issued should be
106 --   coded within this procedure. It is important to note that any 3rd party
107 --   maintenance should be reviewed before placing in this procedure.
108 --
109 -- Access Status:
110 --   Internal Row Handler Use Only.
111 --
112 -- {End Of Comments}
113 -- ----------------------------------------------------------------------------
114 Procedure pre_delete(p_rec in pqp_gds_shd.g_rec_type) is
115 --
116   l_proc  varchar2(72) := g_package||'pre_delete';
117 --
118 Begin
119   hr_utility.set_location('Entering:'||l_proc, 5);
120   --
121   hr_utility.set_location(' Leaving:'||l_proc, 10);
122 End pre_delete;
123 --
124 -- ----------------------------------------------------------------------------
125 -- |-----------------------------< post_delete >------------------------------|
126 -- ----------------------------------------------------------------------------
127 -- {Start Of Comments}
128 --
129 -- Description:
130 --   This private procedure contains any processing which is required after
131 --   the delete dml.
132 --
133 -- Prerequistes:
134 --   This is an internal procedure which is called from the del procedure.
135 --
136 -- In Parameters:
137 --   A Pl/Sql record structure.
138 --
139 -- Post Success:
140 --   Processing continues.
141 --
142 -- Post Failure:
143 --   If an error has occurred, an error message and exception will be raised
144 --   but not handled.
145 --
146 -- Developer Implementation Notes:
147 --   Any post-processing required after the delete dml is issued should be
148 --   coded within this procedure. It is important to note that any 3rd party
149 --   maintenance should be reviewed before placing in this procedure.
150 --
151 -- Access Status:
152 --   Internal Row Handler Use Only.
153 --
154 -- {End Of Comments}
155 -- -----------------------------------------------------------------------------
156 Procedure post_delete(p_rec in pqp_gds_shd.g_rec_type) is
157 --
158   l_proc  varchar2(72) := g_package||'post_delete';
159 --
160 Begin
161   hr_utility.set_location('Entering:'||l_proc, 5);
162   begin
163     --
164     pqp_gds_rkd.after_delete
165       (p_gap_duration_summary_id
166       => p_rec.gap_duration_summary_id
167       ,p_assignment_id_o
168       => pqp_gds_shd.g_old_rec.assignment_id
169       ,p_gap_absence_plan_id_o
170       => pqp_gds_shd.g_old_rec.gap_absence_plan_id
171       ,p_summary_type_o
172       => pqp_gds_shd.g_old_rec.summary_type
173       ,p_gap_level_o
174       => pqp_gds_shd.g_old_rec.gap_level
175       ,p_duration_in_days_o
176       => pqp_gds_shd.g_old_rec.duration_in_days
177       ,p_duration_in_hours_o
178       => pqp_gds_shd.g_old_rec.duration_in_hours
179       ,p_date_start_o
180       => pqp_gds_shd.g_old_rec.date_start
181       ,p_date_end_o
182       => pqp_gds_shd.g_old_rec.date_end
183       ,p_object_version_number_o
184       => pqp_gds_shd.g_old_rec.object_version_number
185       );
186     --
187   exception
188     --
189     when hr_api.cannot_find_prog_unit then
190       --
191       hr_api.cannot_find_prog_unit_error
192         (p_module_name => 'PQP_GAP_DURATION_SUMMARY'
193         ,p_hook_type   => 'AD');
194       --
195   end;
196   --
197   hr_utility.set_location(' Leaving:'||l_proc, 10);
198 End post_delete;
199 --
200 -- ----------------------------------------------------------------------------
201 -- |---------------------------------< del >----------------------------------|
202 -- ----------------------------------------------------------------------------
203 Procedure del
204   (p_rec              in pqp_gds_shd.g_rec_type
205   ) is
206 --
207   l_proc  varchar2(72) := g_package||'del';
208 --
209 Begin
210   hr_utility.set_location('Entering:'||l_proc, 5);
211   --
212   -- We must lock the row which we need to delete.
213   --
214   pqp_gds_shd.lck
215     (p_rec.gap_duration_summary_id
216     ,p_rec.object_version_number
217     );
218   --
219   -- Call the supporting delete validate operation
220   --
221   pqp_gds_bus.delete_validate(p_rec);
222   --
223   -- Call to raise any errors on multi-message list
224   hr_multi_message.end_validation_set;
225   --
226   -- Call the supporting pre-delete operation
227   --
228   pqp_gds_del.pre_delete(p_rec);
229   --
230   -- Delete the row.
231   --
232   pqp_gds_del.delete_dml(p_rec);
233   --
234   -- Call the supporting post-delete operation
235   --
236   pqp_gds_del.post_delete(p_rec);
237   --
238   -- Call to raise any errors on multi-message list
239   hr_multi_message.end_validation_set;
240   --
241 End del;
242 --
243 -- ----------------------------------------------------------------------------
244 -- |---------------------------------< del >----------------------------------|
245 -- ----------------------------------------------------------------------------
246 Procedure del
247   (p_gap_duration_summary_id              in     number
248   ,p_object_version_number                in     number
249   ) is
250 --
251   l_rec   pqp_gds_shd.g_rec_type;
252   l_proc  varchar2(72) := g_package||'del';
253 --
254 Begin
255   hr_utility.set_location('Entering:'||l_proc, 5);
256   --
257   -- As the delete procedure accepts a plsql record structure we do need to
258   -- convert the  arguments into the record structure.
259   -- We don't need to call the supplied conversion argument routine as we
260   -- only need a few attributes.
261   --
262   l_rec.gap_duration_summary_id := p_gap_duration_summary_id;
263   l_rec.object_version_number := p_object_version_number;
264   --
265   -- Having converted the arguments into the pqp_gds_rec
266   -- plsql record structure we must call the corresponding entity
267   -- business process
268   --
269   pqp_gds_del.del(l_rec);
270   --
271   hr_utility.set_location(' Leaving:'||l_proc, 10);
272 End del;
273 --
274 end pqp_gds_del;