1 Package ben_ppl_bus AUTHID CURRENT_USER as
2 /* $Header: bepplrhi.pkh 120.0.12000000.1 2007/01/19 21:49:44 appldev noship $ */
3 --
4 -- ---------------------------------------------------------------------------
5 -- |--------------------------< chk_delete_allowed >-------------------------|
6 -- ---------------------------------------------------------------------------
7 --
8 -- Description:
9 -- Check that a potential life event can be deleted.
10 --
11 -- Prerequisites:
12 -- The record must exist in the database.
13 --
14 -- In Arguments:
15 -- p_ptnl_ler_for_per_id
16 -- p_ptnl_ler_for_per_stat_cd
17 -- p_business_group_id
18 -- p_person_id
19 -- p_ler_id
20 -- p_lf_evt_ocrd_dt
21 --
22 -- Post Success:
23 -- If the value is not found this function will return true.
24 --
25 -- Post Failure:
26 -- An error is raised if the value does not exist.
27 --
28 -- Access Status:
29 -- Internal Development Use Only.
30 --
31 function chk_delete_allowed
32 (p_ptnl_ler_for_per_id in number,
33 p_ptnl_ler_for_per_stat_cd in varchar2,
34 p_business_group_id in number,
35 p_person_id in number,
36 p_ler_id in number,
37 p_lf_evt_ocrd_dt in date) return boolean;
38 --
39 -- ---------------------------------------------------------------------------
40 -- |---------------------< return_legislation_code >-------------------------|
41 -- ---------------------------------------------------------------------------
42 --
43 -- Description:
44 -- Return the legislation code for a specific primary key value
45 --
46 -- Prerequisites:
47 -- The primary key identified by p_ptnl_ler_for_per_id already exists.
48 --
49 -- In Arguments:
50 -- p_ptnl_ler_for_per_id
51 --
52 -- Post Success:
53 -- If the value is found this function will return the values business
54 -- group legislation code.
55 --
56 -- Post Failure:
57 -- An error is raised if the value does not exist.
58 --
59 -- Access Status:
60 -- Internal Development Use Only.
61 --
62 function return_legislation_code
63 (p_ptnl_ler_for_per_id in number) return varchar2;
64 --
65 --
66 -- ----------------------------------------------------------------------------
67 -- |---------------------------< insert_validate >----------------------------|
68 -- ----------------------------------------------------------------------------
69 -- {Start Of Comments}
70 --
71 -- Description:
72 -- This procedure controls the execution of all insert business rules
73 -- validation.
74 --
75 -- Prerequisites:
76 -- This private procedure is called from ins procedure.
77 --
78 -- In Parameters:
79 -- A Pl/Sql record structre.
80 --
81 -- Post Success:
82 -- Processing continues.
83 --
84 -- Post Failure:
85 -- If a business rules fails the error will not be handled by this procedure
86 -- unless explicity coded.
87 --
88 -- Developer Implementation Notes:
89 -- For insert, your business rules should be executed from this procedure and
90 -- should ideally (unless really necessary) just be straight procedure or
91 -- function calls. Try and avoid using conditional branching logic.
92 --
93 -- Access Status:
94 -- Internal Row Handler Use Only.
95 --
96 -- {End Of Comments}
97 -- ----------------------------------------------------------------------------
98 Procedure insert_validate(p_rec in ben_ppl_shd.g_rec_type
99 ,p_effective_date in date);
100 --
101 -- ----------------------------------------------------------------------------
102 -- |---------------------------< update_validate >----------------------------|
103 -- ----------------------------------------------------------------------------
104 -- {Start Of Comments}
105 --
106 -- Description:
107 -- This procedure controls the execution of all update business rules
108 -- validation.
109 --
110 -- Prerequisites:
111 -- This private procedure is called from upd procedure.
112 --
113 -- In Parameters:
114 -- A Pl/Sql record structre.
115 --
116 -- Post Success:
117 -- Processing continues.
118 --
119 -- Post Failure:
120 -- If a business rules fails the error will not be handled by this procedure
121 -- unless explicity coded.
122 --
123 -- Developer Implementation Notes:
124 -- For update, your business rules should be executed from this procedure and
125 -- should ideally (unless really necessary) just be straight procedure or
126 -- function calls. Try and avoid using conditional branching logic.
127 --
128 -- Access Status:
129 -- Internal Row Handler Use Only.
130 --
131 -- {End Of Comments}
132 -- ----------------------------------------------------------------------------
133 Procedure update_validate(p_rec in ben_ppl_shd.g_rec_type
134 ,p_effective_date in date);
135 --
136 -- ----------------------------------------------------------------------------
137 -- |---------------------------< delete_validate >----------------------------|
138 -- ----------------------------------------------------------------------------
139 -- {Start Of Comments}
140 --
141 -- Description:
142 -- This procedure controls the execution of all delete business rules
143 -- validation.
144 --
145 -- Prerequisites:
146 -- This private procedure is called from del procedure.
147 --
148 -- In Parameters:
149 -- A Pl/Sql record structre.
150 --
151 -- Post Success:
152 -- Processing continues.
153 --
154 -- Post Failure:
155 -- If a business rules fails the error will not be handled by this procedure
156 -- unless explicity coded.
157 --
158 -- Developer Implementation Notes:
159 -- For delete, your business rules should be executed from this procedure and
160 -- should ideally (unless really necessary) just be straight procedure or
161 -- function calls. Try and avoid using conditional branching logic.
162 --
163 -- Access Status:
164 -- Internal Row Handler Use Only.
165 --
166 -- {End Of Comments}
167 -- ----------------------------------------------------------------------------
168 Procedure delete_validate(p_rec in ben_ppl_shd.g_rec_type
169 ,p_effective_date in date);
170 --
171 end ben_ppl_bus;
[Home] [Help]