DBA Data[Home] [Help]

PACKAGE BODY: APPS.BEN_PUM_DEL

Source


1 Package Body ben_pum_del as
2 /* $Header: bepumrhi.pkb 120.0 2005/05/28 11:26:51 appldev noship $ */
3 --
4 -- ----------------------------------------------------------------------------
5 -- |                     Private Global Definitions                           |
6 -- ----------------------------------------------------------------------------
7 --
8 g_package  varchar2(33)	:= '  ben_pum_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 ben_pum_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   ben_pum_shd.g_api_dml := true;  -- Set the api dml status
59   --
60   -- Delete the ben_pop_up_messages row.
61   --
62   delete from ben_pop_up_messages
63   where pop_up_messages_id = p_rec.pop_up_messages_id;
64   --
65   ben_pum_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     ben_pum_shd.g_api_dml := false;   -- Unset the api dml status
73     ben_pum_shd.constraint_error
74       (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
75   When Others Then
76     ben_pum_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 ben_pum_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 ben_pum_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     ben_pum_rkd.after_delete
168       (
169   p_pop_up_messages_id            =>p_rec.pop_up_messages_id
170  ,p_pop_name_o                    =>ben_pum_shd.g_old_rec.pop_name
171  ,p_formula_id_o                  =>ben_pum_shd.g_old_rec.formula_id
172  ,p_function_name_o               =>ben_pum_shd.g_old_rec.function_name
173  ,p_block_name_o                  =>ben_pum_shd.g_old_rec.block_name
174  ,p_field_name_o                  =>ben_pum_shd.g_old_rec.field_name
175  ,p_event_name_o                  =>ben_pum_shd.g_old_rec.event_name
176  ,p_message_o                     =>ben_pum_shd.g_old_rec.message
177  ,p_message_type_o                =>ben_pum_shd.g_old_rec.message_type
178  ,p_business_group_id_o           =>ben_pum_shd.g_old_rec.business_group_id
179  ,p_object_version_number_o       =>ben_pum_shd.g_old_rec.object_version_number
180  ,p_start_date_o                  =>ben_pum_shd.g_old_rec.start_date
181  ,p_end_date_o                    =>ben_pum_shd.g_old_rec.end_date
182  ,p_no_formula_flag_o             =>ben_pum_shd.g_old_rec.no_formula_flag
183       );
184     --
185   exception
186     --
187     when hr_api.cannot_find_prog_unit then
188       --
189       hr_api.cannot_find_prog_unit_error
190         (p_module_name => 'ben_pop_up_messages'
191         ,p_hook_type   => 'AD');
192       --
193   end;
194   --
195   -- End of API User Hook for post_delete.
196   --
197   --
198   hr_utility.set_location(' Leaving:'||l_proc, 10);
199 End post_delete;
200 --
201 -- ----------------------------------------------------------------------------
202 -- |---------------------------------< del >----------------------------------|
203 -- ----------------------------------------------------------------------------
204 Procedure del
205   (
206   p_effective_date in date,
207   p_rec	      in ben_pum_shd.g_rec_type
208   ) is
209 --
210   l_proc  varchar2(72) := g_package||'del';
211 --
212 Begin
213   hr_utility.set_location('Entering:'||l_proc, 5);
214   --
215   -- We must lock the row which we need to delete.
216   --
217   ben_pum_shd.lck
218 	(
219 	p_rec.pop_up_messages_id,
220 	p_rec.object_version_number
221 	);
222   --
223   -- Call the supporting delete validate operation
224   --
225   ben_pum_bus.delete_validate(p_rec
226   ,p_effective_date);
227   --
228   -- Call the supporting pre-delete operation
229   --
230   pre_delete(p_rec);
231   --
232   -- Delete the row.
233   --
234   delete_dml(p_rec);
235   --
236   -- Call the supporting post-delete operation
237   --
238   post_delete(
239 p_effective_date,p_rec);
240 End del;
241 --
242 -- ----------------------------------------------------------------------------
243 -- |---------------------------------< del >----------------------------------|
244 -- ----------------------------------------------------------------------------
245 Procedure del
246   (
247   p_effective_date in date,
248   p_pop_up_messages_id                 in number,
249   p_object_version_number              in number
250   ) is
251 --
252   l_rec	  ben_pum_shd.g_rec_type;
253   l_proc  varchar2(72) := g_package||'del';
254 --
255 Begin
256   hr_utility.set_location('Entering:'||l_proc, 5);
257   --
258   -- As the delete procedure accepts a plsql record structure we do need to
259   -- convert the  arguments into the record structure.
260   -- We don't need to call the supplied conversion argument routine as we
261   -- only need a few attributes.
262   --
263   l_rec.pop_up_messages_id:= p_pop_up_messages_id;
264   l_rec.object_version_number := p_object_version_number;
265   --
266   -- Having converted the arguments into the ben_pum_rec
267   -- plsql record structure we must call the corresponding entity
268   -- business process
269   --
270   del(
271     p_effective_date,l_rec);
272   --
273   hr_utility.set_location(' Leaving:'||l_proc, 10);
274 End del;
275 --
276 end ben_pum_del;