1 Package Body pqh_rct_del as
2 /* $Header: pqrctrhi.pkb 115.24 2004/02/19 13:29:18 srajakum noship $ */
3 --
4 -- ----------------------------------------------------------------------------
5 -- | Private Global Definitions |
6 -- ----------------------------------------------------------------------------
7 --
8 g_package varchar2(33) := ' pqh_rct_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 delete the specified row from the schema using the primary key in
19 -- the predicates.
20 -- 2) To trap any constraint violations that may have occurred.
21 -- 3) To raise any other errors.
22 --
23 -- Prerequisites:
24 -- This is an internal private procedure which must be called from the del
25 -- procedure.
26 --
27 -- In Parameters:
28 -- A Pl/Sql record structre.
29 --
30 -- Post Success:
31 -- The specified row will be delete from the schema.
32 --
33 -- Post Failure:
34 -- If a child integrity constraint violation is raised the
35 -- constraint_error procedure will be called.
36 --
37 -- Developer Implementation Notes:
38 -- None.
39 --
40 -- Access Status:
41 -- Internal Row Handler Use Only.
42 --
43 -- {End Of Comments}
44 -- ----------------------------------------------------------------------------
45 Procedure delete_dml(p_rec in pqh_rct_shd.g_rec_type) is
46 --
47 l_proc varchar2(72) := g_package||'delete_dml';
48 --
49 Begin
50 hr_utility.set_location('Entering:'||l_proc, 5);
51 --
52 --
53 -- Delete the pqh_routing_categories row.
54 --
55 delete from pqh_routing_categories
56 where routing_category_id = p_rec.routing_category_id;
57 --
58 --
59 hr_utility.set_location(' Leaving:'||l_proc, 10);
60 --
61 Exception
62 When hr_api.child_integrity_violated then
63 -- Child integrity has been violated
64 pqh_rct_shd.constraint_error
65 (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
66 When Others Then
67 Raise;
68 End delete_dml;
69 --
70 -- ----------------------------------------------------------------------------
71 -- |------------------------------< pre_delete >------------------------------|
72 -- ----------------------------------------------------------------------------
73 -- {Start Of Comments}
74 --
75 -- Description:
76 -- This private procedure contains any processing which is required before
77 -- the delete dml.
78 --
79 -- Prerequisites:
80 -- This is an internal procedure which is called from the del procedure.
81 --
82 -- In Parameters:
83 -- A Pl/Sql record structre.
84 --
85 -- Post Success:
86 -- Processing continues.
87 --
88 -- Post Failure:
89 -- If an error has occurred, an error message and exception will be raised
90 -- but not handled.
91 --
92 -- Developer Implementation Notes:
93 -- Any pre-processing required before the delete dml is issued should be
94 -- coded within this procedure. It is important to note that any 3rd party
95 -- maintenance should be reviewed before placing in this procedure.
96 --
97 -- Access Status:
98 -- Internal Row Handler Use Only.
99 --
100 -- {End Of Comments}
101 -- ----------------------------------------------------------------------------
102 Procedure pre_delete(p_rec in pqh_rct_shd.g_rec_type) is
103 --
104 l_proc varchar2(72) := g_package||'pre_delete';
105 --
106 Begin
107 hr_utility.set_location('Entering:'||l_proc, 5);
108 --
109 hr_utility.set_location(' Leaving:'||l_proc, 10);
110 End pre_delete;
111 --
112 -- ----------------------------------------------------------------------------
113 -- |-----------------------------< post_delete >------------------------------|
114 -- ----------------------------------------------------------------------------
115 -- {Start Of Comments}
116 --
117 -- Description:
118 -- This private procedure contains any processing which is required after the
119 -- delete dml.
120 --
121 -- Prerequisites:
122 -- This is an internal procedure which is called from the del procedure.
123 --
124 -- In Parameters:
125 -- A Pl/Sql record structre.
126 --
127 -- Post Success:
128 -- Processing continues.
129 --
130 -- Post Failure:
131 -- If an error has occurred, an error message and exception will be raised
132 -- but not handled.
133 --
134 -- Developer Implementation Notes:
135 -- Any post-processing required after the delete dml is issued should be
136 -- coded within this procedure. It is important to note that any 3rd party
137 -- maintenance should be reviewed before placing in this procedure.
138 --
139 -- Access Status:
140 -- Internal table Handler Use Only.
141 --
142 -- {End Of Comments}
143 -- ----------------------------------------------------------------------------
144 Procedure post_delete(p_effective_date in date,p_rec in pqh_rct_shd.g_rec_type) is
145 --
146 l_proc varchar2(72) := g_package||'post_delete';
147 --
148 Begin
149 hr_utility.set_location('Entering:'||l_proc, 5);
150 --
151 --
152 -- Start of API User Hook for post_delete.
153 --
154 begin
155 --
156 pqh_rct_rkd.after_delete
157 (
158 p_routing_category_id =>p_rec.routing_category_id
159 ,p_transaction_category_id_o =>pqh_rct_shd.g_old_rec.transaction_category_id
160 ,p_enable_flag_o =>pqh_rct_shd.g_old_rec.enable_flag
161 ,p_default_flag_o =>pqh_rct_shd.g_old_rec.default_flag
162 ,p_delete_flag_o =>pqh_rct_shd.g_old_rec.delete_flag
163 ,p_routing_list_id_o =>pqh_rct_shd.g_old_rec.routing_list_id
164 ,p_position_structure_id_o =>pqh_rct_shd.g_old_rec.position_structure_id
165 ,p_override_position_id_o =>pqh_rct_shd.g_old_rec.override_position_id
166 ,p_override_assignment_id_o =>pqh_rct_shd.g_old_rec.override_assignment_id
167 ,p_override_role_id_o =>pqh_rct_shd.g_old_rec.override_role_id
168 ,p_override_user_id_o =>pqh_rct_shd.g_old_rec.override_user_id
169 ,p_object_version_number_o =>pqh_rct_shd.g_old_rec.object_version_number
170 );
171 --
172 exception
173 --
174 when hr_api.cannot_find_prog_unit then
175 --
176 hr_api.cannot_find_prog_unit_error
177 (p_module_name => 'pqh_routing_categories'
178 ,p_hook_type => 'AD');
179 --
180 end;
181 --
182 -- End of API User Hook for post_delete.
183 --
184 --
185 hr_utility.set_location(' Leaving:'||l_proc, 10);
186 End post_delete;
187 --
188 -- ----------------------------------------------------------------------------
189 -- |---------------------------------< del >----------------------------------|
190 -- ----------------------------------------------------------------------------
191 Procedure del
192 (
193 p_effective_date in date,
194 p_rec in pqh_rct_shd.g_rec_type
195 ) is
196 --
197 l_proc varchar2(72) := g_package||'del';
198 --
199 Begin
200 hr_utility.set_location('Entering:'||l_proc, 5);
201 --
202 -- We must lock the row which we need to delete.
203 --
204 pqh_rct_shd.lck
205 (
206 p_rec.routing_category_id,
207 p_rec.object_version_number
208 );
209 --
210 -- Call the supporting delete validate operation
211 --
212 pqh_rct_bus.delete_validate(p_rec,p_effective_date);
213 --
214 -- Call the supporting pre-delete operation
215 --
216 pre_delete(p_rec);
217 --
218 -- Delete the row.
219 --
220 delete_dml(p_rec);
221 --
222 -- Call the supporting post-delete operation
223 --
224 post_delete(p_effective_date,p_rec);
225 End del;
226 --
227 -- ----------------------------------------------------------------------------
228 -- |---------------------------------< del >----------------------------------|
229 -- ----------------------------------------------------------------------------
230 Procedure del
231 (
232 p_effective_date in date,
233 p_routing_category_id in number,
234 p_object_version_number in number
235 ) is
236 --
237 l_rec pqh_rct_shd.g_rec_type;
238 l_proc varchar2(72) := g_package||'del';
239 --
240 Begin
241 hr_utility.set_location('Entering:'||l_proc, 5);
242 --
243 -- As the delete procedure accepts a plsql record structure we do need to
244 -- convert the arguments into the record structure.
245 -- We don't need to call the supplied conversion argument routine as we
246 -- only need a few attributes.
247 --
248 l_rec.routing_category_id:= p_routing_category_id;
249 l_rec.object_version_number := p_object_version_number;
250 --
251 -- Having converted the arguments into the pqh_rct_rec
252 -- plsql record structure we must call the corresponding entity
253 -- business process
254 --
255 del(p_effective_date,l_rec);
256 --
257 hr_utility.set_location(' Leaving:'||l_proc, 10);
258 End del;
259 --
260 end pqh_rct_del;
[Home] [Help]