1 Package Body pqh_att_del as
2 /* $Header: pqattrhi.pkb 120.3.12000000.2 2007/04/19 12:37:00 brsinha noship $ */
3 --
4 -- ----------------------------------------------------------------------------
5 -- | Private Global Definitions |
6 -- ----------------------------------------------------------------------------
7 --
8 g_package varchar2(33) := ' pqh_att_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_att_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_attributes row.
54 --
55 delete from pqh_attributes
56 where attribute_id = p_rec.attribute_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_att_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_att_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(
145 p_effective_date in date,p_rec in pqh_att_shd.g_rec_type) is
146 --
147 l_proc varchar2(72) := g_package||'post_delete';
148 --
149 Begin
150 hr_utility.set_location('Entering:'||l_proc, 5);
151 --
152 --
153 -- Start of API User Hook for post_delete.
154 --
155 begin
156 --
157 pqh_att_rkd.after_delete
158 (
159 p_attribute_id =>p_rec.attribute_id
160 ,p_attribute_name_o =>pqh_att_shd.g_old_rec.attribute_name
161 ,p_master_attribute_id_o =>pqh_att_shd.g_old_rec.master_attribute_id
162 ,p_master_table_route_id_o =>pqh_att_shd.g_old_rec.master_table_route_id
163 ,p_column_name_o =>pqh_att_shd.g_old_rec.column_name
164 ,p_column_type_o =>pqh_att_shd.g_old_rec.column_type
165 ,p_enable_flag_o =>pqh_att_shd.g_old_rec.enable_flag
166 ,p_width_o =>pqh_att_shd.g_old_rec.width
167 ,p_object_version_number_o =>pqh_att_shd.g_old_rec.object_version_number
168 ,p_region_itemname_o =>pqh_att_shd.g_old_rec.region_itemname
169 ,p_attribute_itemname_o =>pqh_att_shd.g_old_rec.attribute_itemname
170 ,p_decode_function_name_o =>pqh_att_shd.g_old_rec.decode_function_name
171 );
172 --
173 exception
174 --
175 when hr_api.cannot_find_prog_unit then
176 --
177 hr_api.cannot_find_prog_unit_error
178 (p_module_name => 'pqh_attributes'
179 ,p_hook_type => 'AD');
180 --
181 end;
182 --
183 -- End of API User Hook for post_delete.
184 --
185 --
186 hr_utility.set_location(' Leaving:'||l_proc, 10);
187 End post_delete;
188 --
189 -- ----------------------------------------------------------------------------
190 -- |---------------------------------< del >----------------------------------|
191 -- ----------------------------------------------------------------------------
192 Procedure del
193 (
194 p_effective_date in date,
195 p_rec in pqh_att_shd.g_rec_type
196 ) is
197 --
198 l_proc varchar2(72) := g_package||'del';
199 --
200 Begin
201 hr_utility.set_location('Entering:'||l_proc, 5);
202 --
203 -- We must lock the row which we need to delete.
204 --
205 pqh_att_shd.lck
206 (
207 p_rec.attribute_id,
208 p_rec.object_version_number
209 );
210 --
211 -- Call the supporting delete validate operation
212 --
213 pqh_att_bus.delete_validate(p_rec
214 ,p_effective_date);
215 --
216 -- Call the supporting pre-delete operation
217 --
218 pre_delete(p_rec);
219 --
220 -- Delete the row.
221 --
222 delete_dml(p_rec);
223 --
224 -- Call the supporting post-delete operation
225 --
226 post_delete(
227 p_effective_date,p_rec);
228 End del;
229 --
230 -- ----------------------------------------------------------------------------
231 -- |---------------------------------< del >----------------------------------|
232 -- ----------------------------------------------------------------------------
233 Procedure del
234 (
235 p_effective_date in date,
236 p_attribute_id in number,
237 p_object_version_number in number
238 ) is
239 --
240 l_rec pqh_att_shd.g_rec_type;
241 l_proc varchar2(72) := g_package||'del';
242 --
243 Begin
244 hr_utility.set_location('Entering:'||l_proc, 5);
245 --
246 -- As the delete procedure accepts a plsql record structure we do need to
247 -- convert the arguments into the record structure.
248 -- We don't need to call the supplied conversion argument routine as we
249 -- only need a few attributes.
250 --
251 l_rec.attribute_id:= p_attribute_id;
252 l_rec.object_version_number := p_object_version_number;
253 --
254 -- Having converted the arguments into the pqh_att_rec
255 -- plsql record structure we must call the corresponding entity
256 -- business process
257 --
258 del(
259 p_effective_date,l_rec);
260 --
261 hr_utility.set_location(' Leaving:'||l_proc, 10);
262 End del;
263 --
264 end pqh_att_del;
[Home] [Help]