1 Package Body pay_ppd_ins as
2 /* $Header: pyppdrhi.pkb 120.2 2005/12/29 01:38 nprasath noship $ */
3 --
4 -- ----------------------------------------------------------------------------
5 -- | Private Global Definitions |
6 -- ----------------------------------------------------------------------------
7 --
8 g_package varchar2(33) := ' pay_ppd_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_paye_details_id_i number default null;
14 --
15 -- ----------------------------------------------------------------------------
16 -- |------------------------< set_base_key_value >----------------------------|
17 -- ----------------------------------------------------------------------------
18 procedure set_base_key_value
19 (p_paye_details_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 pay_ppd_ins.g_paye_details_id_i := p_paye_details_id;
27 --
28 hr_utility.set_location(' Leaving:'||l_proc, 20);
29 End set_base_key_value;
30 --
31 --
32 -- ----------------------------------------------------------------------------
33 -- |----------------------------< dt_insert_dml >-----------------------------|
34 -- ----------------------------------------------------------------------------
35 -- {Start Of Comments}
36 --
37 -- Description:
38 -- This procedure controls the actual dml insert logic for datetrack. The
39 -- functions of this procedure are as follows:
40 -- 1) Get the object_version_number.
41 -- 2) To set the effective start and end dates to the corresponding
42 -- validation start and end dates. Also, the object version number
43 -- record attribute is set.
44 -- 3) To set and unset the g_api_dml status as required (as we are about to
45 -- perform dml).
46 -- 4) To insert the row into the schema with the derived effective start
47 -- and end dates and the object version number.
48 -- 5) To trap any constraint violations that may have occurred.
49 -- 6) To raise any other errors.
50 --
51 -- Prerequisites:
52 -- This is an internal private procedure which must be called from the
53 -- insert_dml and pre_update (logic permitting) procedure and must have
54 -- all mandatory arguments set.
55 --
56 -- In Parameters:
57 -- A Pl/Sql record structure.
58 --
59 -- Post Success:
60 -- The specified row will be inserted into the schema.
61 --
62 -- Post Failure:
63 -- On the insert dml failure it is important to note that we always reset the
64 -- g_api_dml status to false.
65 -- If a check or unique integrity constraint violation is raised the
66 -- constraint_error procedure will be called.
67 -- If any other error is reported, the error will be raised after the
68 -- g_api_dml status is reset.
69 --
70 -- Developer Implementation Notes:
71 -- This is an internal datetrack maintenance procedure which should
72 -- not be modified in anyway.
73 --
74 -- Access Status:
75 -- Internal Row Handler Use Only.
76 --
77 -- {End Of Comments}
78 -- ----------------------------------------------------------------------------
79 Procedure dt_insert_dml
80 (p_rec in out nocopy pay_ppd_shd.g_rec_type
81 ,p_effective_date in date
82 ,p_datetrack_mode in varchar2
83 ,p_validation_start_date in date
84 ,p_validation_end_date in date
85 ) is
86 -- Cursor to select 'old' created AOL who column values
87 --
88 Cursor C_Sel1 Is
89 select t.created_by,
90 t.creation_date
91 from pay_pl_paye_details_f t
92 where t.paye_details_id = p_rec.paye_details_id
93 and t.effective_start_date =
94 pay_ppd_shd.g_old_rec.effective_start_date
95 and t.effective_end_date = (p_validation_start_date - 1);
96 --
97 l_proc varchar2(72) := g_package||'dt_insert_dml';
98 l_created_by pay_pl_paye_details_f.created_by%TYPE;
99 l_creation_date pay_pl_paye_details_f.creation_date%TYPE;
100 l_last_update_date pay_pl_paye_details_f.last_update_date%TYPE;
101 l_last_updated_by pay_pl_paye_details_f.last_updated_by%TYPE;
102 l_last_update_login pay_pl_paye_details_f.last_update_login%TYPE;
103 --
104 Begin
105 hr_utility.set_location('Entering:'||l_proc, 5);
106 --
107 -- Set the effective start and end dates to the corresponding
108 -- validation start and end dates
109 --
110 p_rec.effective_start_date := p_validation_start_date;
111 p_rec.effective_end_date := p_validation_end_date;
112 --
113 -- If the datetrack_mode is not INSERT then we must populate the WHO
114 -- columns with the 'old' creation values and 'new' updated values.
115 --
116 If (p_datetrack_mode <> hr_api.g_insert) then
117 hr_utility.set_location(l_proc, 10);
118 --
119 -- Get the object version number for the insert
120 --
121 p_rec.object_version_number :=
122 dt_api.get_object_version_number
123 (p_base_table_name => 'pay_pl_paye_details_f'
124 ,p_base_key_column => 'paye_details_id'
125 ,p_base_key_value => p_rec.paye_details_id
126 );
127 --
128 -- Select the 'old' created values
129 --
130 Open C_Sel1;
131 Fetch C_Sel1 Into l_created_by, l_creation_date;
132 If C_Sel1%notfound Then
133 --
134 -- The previous 'old' created row has not been found. We need
135 -- to error as an internal datetrack problem exists.
136 --
137 Close C_Sel1;
138 fnd_message.set_name('PAY', 'HR_6153_ALL_PROCEDURE_FAIL');
139 fnd_message.set_token('PROCEDURE', l_proc);
140 fnd_message.set_token('STEP','10');
141 fnd_message.raise_error;
142 End If;
143 Close C_Sel1;
144 --
145 -- Set the AOL updated WHO values
146 --
147 l_last_update_date := sysdate;
148 l_last_updated_by := fnd_global.user_id;
149 l_last_update_login := fnd_global.login_id;
150 Else
151 p_rec.object_version_number := 1; -- Initialise the object version
152 End If;
153 --
154 --
155 --
156 -- Insert the row into: pay_pl_paye_details_f
157 --
158 insert into pay_pl_paye_details_f
159 (paye_details_id
160 ,effective_start_date
161 ,effective_end_date
162 ,per_or_asg_id
163 ,business_group_id
164 ,contract_category
165 ,object_version_number
166 ,tax_reduction
167 ,tax_calc_with_spouse_child
168 ,income_reduction
169 ,income_reduction_amount
170 ,rate_of_tax
171 ,program_id
172 ,program_login_id
173 ,program_application_id
174 ,request_id
175 ,created_by
176 ,creation_date
177 ,last_update_date
178 ,last_updated_by
179 ,last_update_login
180 )
181 Values
182 (p_rec.paye_details_id
183 ,p_rec.effective_start_date
184 ,p_rec.effective_end_date
185 ,p_rec.per_or_asg_id
186 ,p_rec.business_group_id
187 ,p_rec.contract_category
188 ,p_rec.object_version_number
189 ,p_rec.tax_reduction
190 ,p_rec.tax_calc_with_spouse_child
191 ,p_rec.income_reduction
192 ,p_rec.income_reduction_amount
193 ,p_rec.rate_of_tax
194 ,p_rec.program_id
195 ,p_rec.program_login_id
196 ,p_rec.program_application_id
197 ,p_rec.request_id
198 ,l_created_by
199 ,l_creation_date
200 ,l_last_update_date
201 ,l_last_updated_by
202 ,l_last_update_login
203 );
204 --
205 --
206 hr_utility.set_location(' Leaving:'||l_proc, 15);
207 --
208 Exception
209 When hr_api.check_integrity_violated Then
210 -- A check constraint has been violated
211 --
212 pay_ppd_shd.constraint_error
213 (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
214 When hr_api.unique_integrity_violated Then
215 -- Unique integrity has been violated
216 --
217 pay_ppd_shd.constraint_error
218 (p_constraint_name => hr_api.strip_constraint_name(SQLERRM));
219 When Others Then
220 --
221 Raise;
222 End dt_insert_dml;
223 --
224 -- ----------------------------------------------------------------------------
225 -- |------------------------------< insert_dml >------------------------------|
226 -- ----------------------------------------------------------------------------
227 Procedure insert_dml
228 (p_rec in out nocopy pay_ppd_shd.g_rec_type
229 ,p_effective_date in date
230 ,p_datetrack_mode in varchar2
231 ,p_validation_start_date in date
232 ,p_validation_end_date in date
233 ) is
234 --
235 l_proc varchar2(72) := g_package||'insert_dml';
236 --
237 Begin
238 hr_utility.set_location('Entering:'||l_proc, 5);
239 --
240 pay_ppd_ins.dt_insert_dml
241 (p_rec => p_rec
242 ,p_effective_date => p_effective_date
243 ,p_datetrack_mode => p_datetrack_mode
244 ,p_validation_start_date => p_validation_start_date
245 ,p_validation_end_date => p_validation_end_date
246 );
247 --
248 hr_utility.set_location(' Leaving:'||l_proc, 10);
249 End insert_dml;
250 --
251 -- ----------------------------------------------------------------------------
252 -- |------------------------------< pre_insert >------------------------------|
253 -- ----------------------------------------------------------------------------
254 -- {Start Of Comments}
255 --
256 -- Description:
257 -- This private procedure contains any processing which is required before
258 -- the insert dml. Presently, if the entity has a corresponding primary
259 -- key which is maintained by an associating sequence, the primary key for
260 -- the entity will be populated with the next sequence value in
261 -- preparation for the insert dml.
262 -- Also, if comments are defined for this entity, the comments insert
263 -- logic will also be called, generating a comment_id if required.
264 --
265 -- Prerequisites:
266 -- This is an internal procedure which is called from the ins procedure.
267 --
268 -- In Parameters:
269 -- A Pl/Sql record structure.
270 --
271 -- Post Success:
272 -- Processing continues.
273 --
274 -- Post Failure:
275 -- If an error has occurred, an error message and exception will be raised
276 -- but not handled.
277 --
278 -- Developer Implementation Notes:
279 -- Any pre-processing required before the insert dml is issued should be
280 -- coded within this procedure. As stated above, a good example is the
281 -- generation of a primary key number via a corresponding sequence.
282 -- It is important to note that any 3rd party maintenance should be reviewed
283 -- before placing in this procedure.
284 --
285 -- Access Status:
286 -- Internal Row Handler Use Only.
287 --
288 -- {End Of Comments}
289 -- ----------------------------------------------------------------------------
290 Procedure pre_insert
291 (p_rec in out nocopy pay_ppd_shd.g_rec_type
292 ,p_effective_date in date
293 ,p_datetrack_mode in varchar2
294 ,p_validation_start_date in date
295 ,p_validation_end_date in date
296 ) is
297 --
298 Cursor C_Sel1 is select pay_pl_paye_details_s.nextval from sys.dual;
299 --
300 Cursor C_Sel2 is
301 Select null
302 from pay_pl_paye_details_f
303 where paye_details_id =
304 pay_ppd_ins.g_paye_details_id_i;
305 --
306 l_proc varchar2(72) := g_package||'pre_insert';
307 l_exists varchar2(1);
308 --
309 Begin
310 hr_utility.set_location('Entering:'||l_proc, 5);
311 --
312 If (pay_ppd_ins.g_paye_details_id_i is not null) Then
313 --
314 -- Verify registered primary key values not already in use
315 --
316 Open C_Sel2;
317 Fetch C_Sel2 into l_exists;
318 If C_Sel2%found Then
319 Close C_Sel2;
320 --
321 -- The primary key values are already in use.
322 --
323 fnd_message.set_name('PER','PER_289391_KEY_ALREADY_USED');
324 fnd_message.set_token('TABLE_NAME','pay_pl_paye_details_f');
325 fnd_message.raise_error;
326 End If;
327 Close C_Sel2;
328 --
329 -- Use registered key values and clear globals
330 --
331 p_rec.paye_details_id :=
332 pay_ppd_ins.g_paye_details_id_i;
333 pay_ppd_ins.g_paye_details_id_i := null;
334 Else
335 --
336 -- No registerd key values, so select the next sequence number
337 --
338 --
339 -- Select the next sequence number
340 --
341 Open C_Sel1;
342 Fetch C_Sel1 Into p_rec.paye_details_id;
343 Close C_Sel1;
344 End If;
345 --
346 --
347 hr_utility.set_location(' Leaving:'||l_proc, 10);
348 End pre_insert;
349 --
350 -- ----------------------------------------------------------------------------
351 -- |----------------------------< post_insert >-------------------------------|
352 -- ----------------------------------------------------------------------------
353 -- {Start Of Comments}
354 --
355 -- Description:
356 -- This private procedure contains any processing which is required after
357 -- the insert dml.
358 --
359 -- Prerequisites:
360 -- This is an internal procedure which is called from the ins procedure.
361 --
362 -- In Parameters:
363 -- A Pl/Sql record structure.
364 --
365 -- Post Success:
366 -- Processing continues.
367 --
368 -- Post Failure:
369 -- If an error has occurred, an error message and exception will be raised
370 -- but not handled.
371 --
372 -- Developer Implementation Notes:
373 -- Any post-processing required after the insert dml is issued should be
374 -- coded within this procedure. It is important to note that any 3rd party
375 -- maintenance should be reviewed before placing in this procedure.
376 --
377 -- Access Status:
378 -- Internal Row Handler Use Only.
379 --
380 -- {End Of Comments}
381 -- ----------------------------------------------------------------------------
382 Procedure post_insert
383 (p_rec in pay_ppd_shd.g_rec_type
384 ,p_effective_date in date
385 ,p_datetrack_mode in varchar2
386 ,p_validation_start_date in date
387 ,p_validation_end_date in date
388 ) is
389 --
390 l_proc varchar2(72) := g_package||'post_insert';
391 --
392 Begin
393 hr_utility.set_location('Entering:'||l_proc, 5);
394 begin
395 --
396 pay_ppd_rki.after_insert
397 (p_effective_date
398 => p_effective_date
399 ,p_validation_start_date
400 => p_validation_start_date
401 ,p_validation_end_date
402 => p_validation_end_date
403 ,p_paye_details_id
404 => p_rec.paye_details_id
405 ,p_effective_start_date
406 => p_rec.effective_start_date
407 ,p_effective_end_date
408 => p_rec.effective_end_date
409 -- ,p_per_or_asg_id
410 -- => p_rec.per_or_asg_id
411 -- ,p_business_group_id
412 -- => p_rec.business_group_id
413 -- ,p_contract_category
414 -- => p_rec.contract_category
415 ,p_object_version_number
416 => p_rec.object_version_number
417 ,p_tax_reduction
418 => p_rec.tax_reduction
419 ,p_tax_calc_with_spouse_child
420 => p_rec.tax_calc_with_spouse_child
421 ,p_income_reduction
422 => p_rec.income_reduction
423 ,p_income_reduction_amount
424 => p_rec.income_reduction_amount
425 ,p_rate_of_tax
426 => p_rec.rate_of_tax
427 ,p_program_id
428 => p_rec.program_id
429 ,p_program_login_id
430 => p_rec.program_login_id
431 ,p_program_application_id
432 => p_rec.program_application_id
433 ,p_request_id
434 => p_rec.request_id
435 );
436 --
437 exception
438 --
439 when hr_api.cannot_find_prog_unit then
440 --
441 hr_api.cannot_find_prog_unit_error
442 (p_module_name => 'PAY_PL_PAYE_DETAILS_F'
443 ,p_hook_type => 'AI');
444 --
445 end;
446 --
447 hr_utility.set_location(' Leaving:'||l_proc, 10);
448 End post_insert;
449 --
450 -- ----------------------------------------------------------------------------
451 -- |-------------------------------< ins_lck >--------------------------------|
452 -- ----------------------------------------------------------------------------
453 -- {Start Of Comments}
454 --
455 -- Description:
456 -- The ins_lck process has one main function to perform. When inserting
457 -- a datetracked row, we must validate the DT mode.
458 --
459 -- Prerequisites:
460 -- This procedure can only be called for the datetrack mode of INSERT.
461 --
462 -- In Parameters:
463 --
464 -- Post Success:
465 -- On successful completion of the ins_lck process the parental
466 -- datetracked rows will be locked providing the p_enforce_foreign_locking
467 -- argument value is TRUE.
468 -- If the p_enforce_foreign_locking argument value is FALSE then the
469 -- parential rows are not locked.
470 --
471 -- Post Failure:
472 -- The Lck process can fail for:
473 -- 1) When attempting to lock the row the row could already be locked by
474 -- another user. This will raise the HR_Api.Object_Locked exception.
475 -- 2) When attempting to the lock the parent which doesn't exist.
476 -- For the entity to be locked the parent must exist!
477 --
478 -- Developer Implementation Notes:
479 -- None.
480 --
481 -- Access Status:
482 -- Internal Row Handler Use Only.
483 --
484 -- {End Of Comments}
485 -- ----------------------------------------------------------------------------
486 Procedure ins_lck
487 (p_effective_date in date
488 ,p_datetrack_mode in varchar2
489 ,p_rec in pay_ppd_shd.g_rec_type
490 ,p_validation_start_date out nocopy date
491 ,p_validation_end_date out nocopy date
492 ) is
493 --
494 l_proc varchar2(72) := g_package||'ins_lck';
495 l_validation_start_date date;
496 l_validation_end_date date;
497 --
498 Begin
499 hr_utility.set_location('Entering:'||l_proc, 5);
500 --
501 -- Validate the datetrack mode mode getting the validation start
502 -- and end dates for the specified datetrack operation.
503 --
504
505 if p_rec.contract_category in ('CIVIL','TERM_NORMAL','LUMP','F_LUMP') then
506
507 dt_api.validate_dt_mode
508 (p_effective_date => p_effective_date
509 ,p_datetrack_mode => p_datetrack_mode
510 ,p_base_table_name => 'pay_pl_paye_details_f'
511 ,p_base_key_column => 'paye_details_id'
512 ,p_base_key_value => p_rec.paye_details_id
513 ,p_parent_table_name1 => 'per_all_assignments_f'
514 ,p_parent_key_column1 => 'assignment_id'
515 ,p_parent_key_value1 => p_rec.per_or_asg_id
516 ,p_enforce_foreign_locking => true
517 ,p_validation_start_date => l_validation_start_date
518 ,p_validation_end_date => l_validation_end_date
519 );
520
521 elsif p_rec.contract_category = 'NORMAL' then
522
523 dt_api.validate_dt_mode
524 (p_effective_date => p_effective_date
525 ,p_datetrack_mode => p_datetrack_mode
526 ,p_base_table_name => 'pay_pl_paye_details_f'
527 ,p_base_key_column => 'paye_details_id'
528 ,p_base_key_value => p_rec.paye_details_id
529 ,p_parent_table_name1 => 'per_people_f'
530 ,p_parent_key_column1 => 'person_id'
531 ,p_parent_key_value1 => p_rec.per_or_asg_id
532 ,p_enforce_foreign_locking => true
533 ,p_validation_start_date => l_validation_start_date
534 ,p_validation_end_date => l_validation_end_date
535 );
536
537 end if;
538
539 /* dt_api.validate_dt_mode
540 (p_effective_date => p_effective_date
541 ,p_datetrack_mode => p_datetrack_mode
542 ,p_base_table_name => 'pay_pl_paye_details_f'
543 ,p_base_key_column => 'paye_details_id'
544 ,p_base_key_value => p_rec.paye_details_id
545 ,p_enforce_foreign_locking => true
546 ,p_validation_start_date => l_validation_start_date
547 ,p_validation_end_date => l_validation_end_date
548 );*/
549 --
550 -- Set the validation start and end date OUT arguments
551 --
552 p_validation_start_date := l_validation_start_date;
553 p_validation_end_date := l_validation_end_date;
554 --
555 hr_utility.set_location(' Leaving:'||l_proc, 10);
556 --
557 End ins_lck;
558 --
559 -- ----------------------------------------------------------------------------
560 -- |---------------------------------< ins >----------------------------------|
561 -- ----------------------------------------------------------------------------
562 Procedure ins
563 (p_effective_date in date
564 ,p_rec in out nocopy pay_ppd_shd.g_rec_type
565 ) is
566 --
567 l_proc varchar2(72) := g_package||'ins';
568 l_datetrack_mode varchar2(30) := hr_api.g_insert;
569 l_validation_start_date date;
570 l_validation_end_date date;
571 --
572 Begin
573 hr_utility.set_location('Entering:'||l_proc, 5);
574 --
575 -- Call the lock operation
576 --
577 pay_ppd_ins.ins_lck
578 (p_effective_date => p_effective_date
579 ,p_datetrack_mode => l_datetrack_mode
580 ,p_rec => p_rec
581 ,p_validation_start_date => l_validation_start_date
582 ,p_validation_end_date => l_validation_end_date
583 );
584 --
585 -- Call the supporting insert validate operations
586 --
587 pay_ppd_bus.insert_validate
588 (p_rec => p_rec
589 ,p_effective_date => p_effective_date
590 ,p_datetrack_mode => l_datetrack_mode
591 ,p_validation_start_date => l_validation_start_date
592 ,p_validation_end_date => l_validation_end_date
593 );
594 --
595 -- Call to raise any errors on multi-message list
596 hr_multi_message.end_validation_set;
597 --
598 -- Call the supporting pre-insert operation
599 --
600 pay_ppd_ins.pre_insert
601 (p_rec => p_rec
602 ,p_effective_date => p_effective_date
603 ,p_datetrack_mode => l_datetrack_mode
604 ,p_validation_start_date => l_validation_start_date
605 ,p_validation_end_date => l_validation_end_date
606 );
607 --
608 -- Insert the row
609 --
610
611 pay_ppd_ins.insert_dml
612 (p_rec => p_rec
613 ,p_effective_date => p_effective_date
614 ,p_datetrack_mode => l_datetrack_mode
615 ,p_validation_start_date => l_validation_start_date
616 ,p_validation_end_date => l_validation_end_date
617 );
618 --
619 -- Call the supporting post-insert operation
620 --
621 pay_ppd_ins.post_insert
622 (p_rec => p_rec
623 ,p_effective_date => p_effective_date
624 ,p_datetrack_mode => l_datetrack_mode
625 ,p_validation_start_date => l_validation_start_date
626 ,p_validation_end_date => l_validation_end_date
627 );
628 --
629 -- Call to raise any errors on multi-message list
630 hr_multi_message.end_validation_set;
631 --
632 hr_utility.set_location('Leaving:'||l_proc,10);
633 end ins;
634 --
635 -- ----------------------------------------------------------------------------
636 -- |---------------------------------< ins >----------------------------------|
637 -- ----------------------------------------------------------------------------
638 Procedure ins
639 (p_effective_date in date
640 ,p_per_or_asg_id in number
641 ,p_business_group_id in number
642 ,p_contract_category in varchar2
643 ,p_tax_reduction in varchar2 default null
644 ,p_tax_calc_with_spouse_child in varchar2 default null
645 ,p_income_reduction in varchar2 default null
646 ,p_income_reduction_amount in number default null
647 ,p_rate_of_tax in varchar2 default null
648 ,p_program_id in number default null
649 ,p_program_login_id in number default null
650 ,p_program_application_id in number default null
651 ,p_request_id in number default null
652 ,p_paye_details_id out nocopy number
653 ,p_object_version_number out nocopy number
654 ,p_effective_start_date out nocopy date
655 ,p_effective_end_date out nocopy date
656 ) is
657 --
658 l_rec pay_ppd_shd.g_rec_type;
659 l_proc varchar2(72) := g_package||'ins';
660 --
661 Begin
662 hr_utility.set_location('Entering:'||l_proc, 5);
663 --
664 -- Call conversion function to turn arguments into the
665 -- p_rec structure.
666 --
667 l_rec :=
668 pay_ppd_shd.convert_args
669 (null
670 ,null
671 ,null
672 ,p_per_or_asg_id
673 ,p_business_group_id
674 ,p_contract_category
675 ,null
676 ,p_tax_reduction
677 ,p_tax_calc_with_spouse_child
678 ,p_income_reduction
679 ,p_income_reduction_amount
680 ,p_rate_of_tax
681 ,p_program_id
682 ,p_program_login_id
683 ,p_program_application_id
684 ,p_request_id
685 );
686 --
687 -- Having converted the arguments into the pay_ppd_rec
688 -- plsql record structure we call the corresponding record
689 -- business process.
690 --
691
692 pay_ppd_ins.ins
693 (p_effective_date
694 ,l_rec
695 );
696 --
697 -- Set the OUT arguments.
698 --
699 p_paye_details_id := l_rec.paye_details_id;
700 p_effective_start_date := l_rec.effective_start_date;
701 p_effective_end_date := l_rec.effective_end_date;
702 p_object_version_number := l_rec.object_version_number;
703 --
704 --
705 hr_utility.set_location(' Leaving:'||l_proc, 10);
706 End ins;
707 --
708 end pay_ppd_ins;
[Home] [Help]