1 Package Body irc_cmt_ins as
2 /* $Header: ircmtrhi.pkb 120.1 2008/03/18 14:03:16 amikukum noship $ */
3 --
4 -- ----------------------------------------------------------------------------
5 -- | Private Global Definitions |
6 -- ----------------------------------------------------------------------------
7 --
8 g_package varchar2(33) := ' irc_cmt_ins.'; -- Global package name
9 --
10 -- The following global variables are only to be used by
11 -- the set_base_key_value and pre_insert procedures.
12 --
13 g_communication_topic_id_i number default null;
14 --
15 -- ----------------------------------------------------------------------------
16 -- |------------------------< set_base_key_value >----------------------------|
17 -- ----------------------------------------------------------------------------
18 procedure set_base_key_value
19 (p_communication_topic_id in number) is
20 --
21 l_proc varchar2(72) := g_package||'set_base_key_value';
22 --
23 Begin
24 hr_utility.set_location('Entering:'||l_proc, 10);
25 --
26 irc_cmt_ins.g_communication_topic_id_i := p_communication_topic_id;
27 --
28 hr_utility.set_location(' Leaving:'||l_proc, 20);
29 End set_base_key_value;
30 --
31 --
32 -- ----------------------------------------------------------------------------
33 -- |------------------------------< insert_dml >------------------------------|
34 -- ----------------------------------------------------------------------------
35 -- {Start Of Comments}
36 --
37 -- Description:
38 -- This procedure controls the actual dml insert logic. The processing of
39 -- this procedure are as follows:
40 -- 1) Initialise the object_version_number to 1 if the object_version_number
41 -- is defined as an attribute for this entity.
42 -- 2) To set and unset the g_api_dml status as required (as we are about to
43 -- perform dml).
44 -- 3) To insert the row into the schema.
45 -- 4) To trap any constraint violations that may have occurred.
46 -- 5) To raise any other errors.
47 --
48 -- Prerequisites:
49 -- This is an internal private procedure which must be called from the ins
50 -- procedure and must have all mandatory attributes set (except the
51 -- object_version_number which is initialised within this procedure).
52 --
53 -- In Parameters:
54 -- A Pl/Sql record structre.
55 --
56 -- Post Success:
57 -- The specified row will be inserted into the schema.
58 --
59 -- Post Failure:
60 -- On the insert dml failure it is important to note that we always reset the
61 -- g_api_dml status to false.
62 -- If a check, unique or parent integrity constraint violation is raised the
63 -- constraint_error procedure will be called.
64 -- If any other error is reported, the error will be raised after the
65 -- g_api_dml status is reset.
66 --
67 -- Developer Implementation Notes:
68 -- None.
69 --
70 -- Access Status:
71 -- Internal Row Handler Use Only.
72 --
73 -- {End Of Comments}
74 -- ----------------------------------------------------------------------------
75 Procedure insert_dml
76 (p_rec in out nocopy irc_cmt_shd.g_rec_type
77 ) is
78 --
79 l_proc varchar2(72) := g_package||'insert_dml';
80 --
81 Begin
82 hr_utility.set_location('Entering:'||l_proc, 5);
83 p_rec.object_version_number := 1; -- Initialise the object version
84 --
85 --
86 --
87 -- Insert the row into: irc_comm_topics
88 --
89 insert into irc_comm_topics
90 (communication_topic_id
91 ,communication_id
92 ,subject
93 ,status
94 ,object_version_number
95 )
96 Values
97 (p_rec.communication_topic_id
98 ,p_rec.communication_id
99 ,p_rec.subject
100 ,p_rec.status
101 ,p_rec.object_version_number
102 );
103 --
104 --
105 --
106 hr_utility.set_location(' Leaving:'||l_proc, 10);
107 Exception
108 When hr_api.check_integrity_violated Then
109 -- A check constraint has been violated
110 --
111 irc_cmt_shd.constraint_error
112 (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
113 When hr_api.parent_integrity_violated Then
114 -- Parent integrity has been violated
115 --
116 irc_cmt_shd.constraint_error
117 (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
118 When hr_api.unique_integrity_violated Then
119 -- Unique integrity has been violated
120 --
121 irc_cmt_shd.constraint_error
122 (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
123 When Others Then
124 --
125 Raise;
126 End insert_dml;
127 --
128 -- ----------------------------------------------------------------------------
129 -- |------------------------------< pre_insert >------------------------------|
130 -- ----------------------------------------------------------------------------
131 -- {Start Of Comments}
132 --
133 -- Description:
134 -- This private procedure contains any processing which is required before
135 -- the insert dml. Presently, if the entity has a corresponding primary
136 -- key which is maintained by an associating sequence, the primary key for
137 -- the entity will be populated with the next sequence value in
138 -- preparation for the insert dml.
139 --
140 -- Prerequisites:
141 -- This is an internal procedure which is called from the ins procedure.
142 --
143 -- In Parameters:
144 -- A Pl/Sql record structure.
145 --
146 -- Post Success:
147 -- Processing continues.
148 --
149 -- Post Failure:
150 -- If an error has occurred, an error message and exception will be raised
151 -- but not handled.
152 --
153 -- Developer Implementation Notes:
154 -- Any pre-processing required before the insert dml is issued should be
155 -- coded within this procedure. As stated above, a good example is the
156 -- generation of a primary key number via a corresponding sequence.
157 -- It is important to note that any 3rd party maintenance should be reviewed
158 -- before placing in this procedure.
159 --
160 -- Access Status:
161 -- Internal Row Handler Use Only.
162 --
163 -- {End Of Comments}
164 -- ----------------------------------------------------------------------------
165 Procedure pre_insert
166 (p_rec in out nocopy irc_cmt_shd.g_rec_type
167 ) is
168 --
169 Cursor C_Sel1 is select irc_comm_topics_s.nextval from sys.dual;
170 --
171 Cursor C_Sel2 is
172 Select null
173 from irc_comm_topics
174 where communication_topic_id =
175 irc_cmt_ins.g_communication_topic_id_i;
176 --
177 l_proc varchar2(72) := g_package||'pre_insert';
178 l_exists varchar2(1);
179 --
180 Begin
181 hr_utility.set_location('Entering:'||l_proc, 5);
182 --
183 If (irc_cmt_ins.g_communication_topic_id_i is not null) Then
184 --
185 -- Verify registered primary key values not already in use
186 --
187 Open C_Sel2;
188 Fetch C_Sel2 into l_exists;
189 If C_Sel2%found Then
190 Close C_Sel2;
191 --
192 -- The primary key values are already in use.
193 --
194 fnd_message.set_name('PER','PER_289391_KEY_ALREADY_USED');
195 fnd_message.set_token('TABLE_NAME','irc_comm_topics');
196 fnd_message.raise_error;
197 End If;
198 Close C_Sel2;
199 --
200 -- Use registered key values and clear globals
201 --
202 p_rec.communication_topic_id :=
203 irc_cmt_ins.g_communication_topic_id_i;
204 irc_cmt_ins.g_communication_topic_id_i := null;
205 Else
206 --
207 -- No registerd key values, so select the next sequence number
208 --
209 --
210 -- Select the next sequence number
211 --
212 Open C_Sel1;
213 Fetch C_Sel1 Into p_rec.communication_topic_id;
214 Close C_Sel1;
215 End If;
216 --
217 hr_utility.set_location(' Leaving:'||l_proc, 10);
218 End pre_insert;
219 --
220 -- ----------------------------------------------------------------------------
221 -- |-----------------------------< post_insert >------------------------------|
222 -- ----------------------------------------------------------------------------
223 -- {Start Of Comments}
224 --
225 -- Description:
226 -- This private procedure contains any processing which is required after
227 -- the insert dml.
228 --
229 -- Prerequisites:
230 -- This is an internal procedure which is called from the ins procedure.
231 --
232 -- In Parameters:
233 -- A Pl/Sql record structre.
234 --
235 -- Post Success:
236 -- Processing continues.
237 --
238 -- Post Failure:
239 -- If an error has occurred, an error message and exception will be raised
240 -- but not handled.
241 --
242 -- Developer Implementation Notes:
243 -- Any post-processing required after the insert dml is issued should be
244 -- coded within this procedure. It is important to note that any 3rd party
245 -- maintenance should be reviewed before placing in this procedure.
246 --
247 -- Access Status:
248 -- Internal Row Handler Use Only.
249 --
250 -- {End Of Comments}
251 -- ----------------------------------------------------------------------------
252 Procedure post_insert
253 (p_effective_date in date
254 ,p_rec in irc_cmt_shd.g_rec_type
255 ) is
256 --
257 l_proc varchar2(72) := g_package||'post_insert';
258 --
259 Begin
260 hr_utility.set_location('Entering:'||l_proc, 5);
261 begin
262 --
263 irc_cmt_rki.after_insert
264 (p_effective_date => p_effective_date
265 ,p_communication_topic_id
266 => p_rec.communication_topic_id
267 ,p_communication_id
268 => p_rec.communication_id
269 ,p_subject
270 => p_rec.subject
271 ,p_status
272 => p_rec.status
273 ,p_object_version_number
274 => p_rec.object_version_number
275 );
276 --
277 exception
278 --
279 when hr_api.cannot_find_prog_unit then
280 --
281 hr_api.cannot_find_prog_unit_error
282 (p_module_name => 'IRC_COMM_TOPICS'
283 ,p_hook_type => 'AI');
284 --
285 end;
286 --
287 hr_utility.set_location(' Leaving:'||l_proc, 10);
288 End post_insert;
289 --
290 -- ----------------------------------------------------------------------------
291 -- |---------------------------------< ins >----------------------------------|
292 -- ----------------------------------------------------------------------------
293 Procedure ins
294 (p_effective_date in date
295 ,p_rec in out nocopy irc_cmt_shd.g_rec_type
296 ) is
297 --
298 l_proc varchar2(72) := g_package||'ins';
299 --
300 Begin
301 hr_utility.set_location('Entering:'||l_proc, 5);
302 --
303 -- Call the supporting insert validate operations
304 --
305 irc_cmt_bus.insert_validate
306 (p_effective_date
307 ,p_rec
308 );
309 --
310 -- Call to raise any errors on multi-message list
311 hr_multi_message.end_validation_set;
312 --
313 -- Call the supporting pre-insert operation
314 --
315 irc_cmt_ins.pre_insert(p_rec);
316 --
317 -- Insert the row
318 --
319 irc_cmt_ins.insert_dml(p_rec);
320 --
321 -- Call the supporting post-insert operation
322 --
323 irc_cmt_ins.post_insert
324 (p_effective_date
325 ,p_rec
326 );
327 --
328 -- Call to raise any errors on multi-message list
329 hr_multi_message.end_validation_set;
330 --
331 hr_utility.set_location('Leaving:'||l_proc, 20);
332 end ins;
333 --
334 -- ----------------------------------------------------------------------------
335 -- |---------------------------------< ins >----------------------------------|
336 -- ----------------------------------------------------------------------------
337 Procedure ins
338 (p_effective_date in date
339 ,p_communication_id in number
340 ,p_subject in varchar2
341 ,p_status in varchar2
342 ,p_communication_topic_id out nocopy number
343 ,p_object_version_number out nocopy number
344 ) is
345 --
346 l_rec irc_cmt_shd.g_rec_type;
347 l_proc varchar2(72) := g_package||'ins';
348 --
349 Begin
350 hr_utility.set_location('Entering:'||l_proc, 5);
351 --
352 -- Call conversion function to turn arguments into the
353 -- p_rec structure.
354 --
355 l_rec :=
356 irc_cmt_shd.convert_args
357 (null
358 ,p_communication_id
359 ,p_subject
360 ,p_status
361 ,null
362 );
363 --
364 -- Having converted the arguments into the irc_cmt_rec
365 -- plsql record structure we call the corresponding record business process.
366 --
367 irc_cmt_ins.ins
368 (p_effective_date
369 ,l_rec
370 );
371 --
372 -- As the primary key argument(s)
373 -- are specified as an OUT's we must set these values.
374 --
375 p_communication_topic_id := l_rec.communication_topic_id;
376 p_object_version_number := l_rec.object_version_number;
377 --
378 hr_utility.set_location(' Leaving:'||l_proc, 10);
379 End ins;
380 --
381 end irc_cmt_ins;
[Home] [Help]