DBA Data[Home] [Help]

PACKAGE BODY: APPS.PER_PYP_DEL

Source


1 Package Body per_pyp_del as
2 /* $Header: pepyprhi.pkb 120.24 2011/09/28 10:47:13 akaranam ship $ */
3 --
4 -- ----------------------------------------------------------------------------
5 -- |                     Private Global Definitions                           |
6 -- ----------------------------------------------------------------------------
7 --
8 g_package  varchar2(33) := '  per_pyp_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 -- Pre Conditions:
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 Table Handler Use Only.
48 --
49 -- {End Of Comments}
50 -- ----------------------------------------------------------------------------
51 Procedure delete_dml(p_rec in per_pyp_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   per_pyp_shd.g_api_dml := true;  -- Set the api dml status
59   --
60   -- Delete the per_pay_proposals row.
61   --
62   delete from per_pay_proposals
63   where pay_proposal_id = p_rec.pay_proposal_id;
64   --
65   per_pyp_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     per_pyp_shd.g_api_dml := false;   -- Unset the api dml status
73     per_pyp_shd.constraint_error
74       (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
75   When Others Then
76     per_pyp_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 -- Pre Conditions:
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 Table Handler Use Only.
109 --
110 -- {End Of Comments}
111 -- ----------------------------------------------------------------------------
112 Procedure pre_delete(p_rec in per_pyp_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 -- Pre Conditions:
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(p_rec in per_pyp_shd.g_rec_type) is
155 --
156   l_proc  varchar2(72) := g_package||'post_delete';
157 --
158 Begin
159   hr_utility.set_location('Entering:'||l_proc, 5);
160   --
161   -- Call to user hook for post_delete.
162   --
163   begin
164 --
165   per_pyp_rkd.after_delete
166     (
167      p_pay_proposal_id              => p_rec.pay_proposal_id,
168      p_assignment_id_o              => per_pyp_shd.g_old_rec.assignment_id,
169      p_business_group_id_o          => per_pyp_shd.g_old_rec.business_group_id,
170      p_change_date_o                => per_pyp_shd.g_old_rec.change_date,
171      p_comments_o                   => per_pyp_shd.g_old_rec.comments,
172      p_next_sal_review_date_o       => per_pyp_shd.g_old_rec.next_sal_review_date,
173      p_proposal_reason_o            => per_pyp_shd.g_old_rec.proposal_reason,
174      p_proposed_salary_n_o          => per_pyp_shd.g_old_rec.proposed_salary_n,
175      p_forced_ranking_o             => per_pyp_shd.g_old_rec.forced_ranking,
176      p_date_to_o        => per_pyp_shd.g_old_rec.date_to,
177      p_performance_review_id_o      => per_pyp_shd.g_old_rec.performance_review_id,
178      p_attribute_category_o         => per_pyp_shd.g_old_rec.attribute_category,
179      p_attribute1_o                 => per_pyp_shd.g_old_rec.attribute1,
180      p_attribute2_o                 => per_pyp_shd.g_old_rec.attribute2,
181      p_attribute3_o                 => per_pyp_shd.g_old_rec.attribute3,
182      p_attribute4_o                 => per_pyp_shd.g_old_rec.attribute4,
183      p_attribute5_o                 => per_pyp_shd.g_old_rec.attribute5,
184      p_attribute6_o                 => per_pyp_shd.g_old_rec.attribute6,
185      p_attribute7_o                 => per_pyp_shd.g_old_rec.attribute7,
186      p_attribute8_o                 => per_pyp_shd.g_old_rec.attribute8,
187      p_attribute9_o                 => per_pyp_shd.g_old_rec.attribute9,
188      p_attribute10_o                => per_pyp_shd.g_old_rec.attribute10,
189      p_attribute11_o                => per_pyp_shd.g_old_rec.attribute11,
190      p_attribute12_o                => per_pyp_shd.g_old_rec.attribute12,
191      p_attribute13_o                => per_pyp_shd.g_old_rec.attribute13,
192      p_attribute14_o                => per_pyp_shd.g_old_rec.attribute14,
193      p_attribute15_o                => per_pyp_shd.g_old_rec.attribute15,
194      p_attribute16_o                => per_pyp_shd.g_old_rec.attribute16,
195      p_attribute17_o                => per_pyp_shd.g_old_rec.attribute17,
196      p_attribute18_o                => per_pyp_shd.g_old_rec.attribute18,
197      p_attribute19_o                => per_pyp_shd.g_old_rec.attribute19,
198      p_attribute20_o                => per_pyp_shd.g_old_rec.attribute20,
199      p_object_version_number_o      => per_pyp_shd.g_old_rec.object_version_number,
200      p_multiple_components_o        => per_pyp_shd.g_old_rec.multiple_components,
201      p_approved_o                   => per_pyp_shd.g_old_rec.approved
202     );
203 --
204   exception
205     when hr_api.cannot_find_prog_unit then
206       hr_api.cannot_find_prog_unit_error
207         (p_module_name => 'PER_PAY_PROPOSALS'
208         ,p_hook_type  => 'AD'
209         );
210   end;
211   -- End of API User Hook for post_delete.
212   hr_utility.set_location(' Leaving:'||l_proc, 10);
213 End post_delete;
214 --
215 -- ----------------------------------------------------------------------------
216 -- |---------------------------------< del >----------------------------------|
217 -- ----------------------------------------------------------------------------
218 Procedure del
219   (
220   p_rec           in  per_pyp_shd.g_rec_type,
221   p_validate      in  boolean,
222   p_salary_warning   out nocopy boolean
223   ) is
224 --
225   l_proc     varchar2(72) := g_package||'del';
226 --
227 Begin
228   hr_utility.set_location('Entering:'||l_proc, 5);
229   --
230   -- Determine if the business process is to be validated.
231   --
232   If p_validate then
233     --
234     -- Issue the savepoint.
235     --
236     SAVEPOINT del_per_pyp;
237   End If;
238   --
239   -- We must lock the row which we need to delete.
240   --
241   per_pyp_shd.lck
242   (
243   p_rec.pay_proposal_id,
244   p_rec.object_version_number
245   );
246   --
247   -- Call the supporting delete validate operation
248   --
249   per_pyp_bus.delete_validate
250      (p_rec            =>p_rec
251      ,p_salary_warning     =>p_salary_warning
252      );
253   --
254   -- Call the supporting pre-delete operation
255   --
256   pre_delete(p_rec);
257   --
258   -- Delete the row.
259   --
260   delete_dml(p_rec);
261   --
262   -- Call the supporting post-delete operation
263   --
264   post_delete(p_rec);
265   --
266   -- If we are validating then raise the Validate_Enabled exception
267   --
268   If p_validate then
269     Raise HR_Api.Validate_Enabled;
270   End If;
271   --
272   hr_utility.set_location(' Leaving:'||l_proc, 10);
273 Exception
274   When HR_Api.Validate_Enabled Then
275     --
276     -- As the Validate_Enabled exception has been raised
277     -- we must rollback to the savepoint
278     --
279     ROLLBACK TO del_per_pyp;
280 End del;
281 --
282 -- ----------------------------------------------------------------------------
283 -- |---------------------------------< del >----------------------------------|
284 -- ----------------------------------------------------------------------------
285 Procedure del
286   (
287   p_pay_proposal_id                    in number,
288   p_object_version_number              in number,
289   p_validate                           in boolean,
290   p_salary_warning               out nocopy boolean
291 
292   ) is
293 --
294   l_rec   per_pyp_shd.g_rec_type;
295   l_proc  varchar2(72) := g_package||'del';
296 --
297 Begin
298   hr_utility.set_location('Entering:'||l_proc, 5);
299   --
300   -- As the delete procedure accepts a plsql record structure we do need to
301   -- convert the  arguments into the record structure.
302   -- We don't need to call the supplied conversion argument routine as we
303   -- only need a few attributes.
304   --
305   l_rec.pay_proposal_id:= p_pay_proposal_id;
306   l_rec.object_version_number := p_object_version_number;
307   --
308   -- Having converted the arguments into the per_pyp_rec
309   -- plsql record structure we must call the corresponding entity
310   -- business process
311   --
312   del(p_rec   => l_rec
313      ,p_validate  => p_validate
314      ,p_salary_warning  => p_salary_warning
315       );
316 
317   --
318   hr_utility.set_location(' Leaving:'||l_proc, 10);
319 End del;
320 --
321 end per_pyp_del;