1 Package per_rol_bus as
2 /* $Header: perolrhi.pkh 120.0 2005/05/31 18:35:08 appldev noship $ */
3 --
4 -- ---------------------------------------------------------------------------
5 -- |----------------------< set_security_group_id >--------------------------|
6 -- ---------------------------------------------------------------------------
7 -- {Start Of Comments}
8 --
9 -- Description:
10 -- Sets the security_group_id in CLIENT_INFO for the appropriate business
11 -- group context.
12 --
13 -- Prerequisites:
14 -- The primary key identified by p_role_id
15 -- already exists.
16 --
17 -- In Arguments:
18 -- p_role_id
19 --
20 --
21 -- Post Success:
22 -- The security_group_id will be set in CLIENT_INFO.
23 --
24 -- Post Failure:
25 -- An error is raised if the value does not exist.
26 --
27 -- Access Status:
28 -- Internal Development Use Only.
29 --
30 -- {End Of Comments}
31 -- ---------------------------------------------------------------------------
32 procedure set_security_group_id
33 (p_role_id in number
34 );
35 --
36 --
37 -- ---------------------------------------------------------------------------
38 -- |---------------------< return_legislation_code >-------------------------|
39 -- ---------------------------------------------------------------------------
40 -- {Start Of Comments}
41 --
42 -- Description:
43 -- Return the legislation code for a specific primary key value
44 --
45 -- Prerequisites:
46 -- The primary key identified by p_role_id
47 -- already exists.
48 --
49 -- In Arguments:
50 -- p_role_id
51 --
52 --
53 -- Post Success:
54 -- The business group's legislation code will be returned.
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 -- {End Of Comments}
63 -- ---------------------------------------------------------------------------
64 FUNCTION return_legislation_code
65 (p_role_id in number
66 ) RETURN varchar2;
67 --
68 --
69 -- ----------------------------------------------------------------------------
70 -- |---------------------------< insert_validate >----------------------------|
71 -- ----------------------------------------------------------------------------
72 -- {Start of comments}
73 --
74 -- Description:
75 -- This procedure controls the execution of all insert business rules
76 -- validation.
77 --
78 -- Prerequisites:
79 -- This private procedure is called from ins procedure.
80 --
81 -- In Parameters:
82 -- A Pl/Sql record structure.
83 --
84 -- Post Success:
85 -- Processing continues.
86 --
87 -- Post Failure:
88 -- If a business rules fails the error will not be handled by this procedure
89 -- unless explicity coded.
90 --
91 -- Developer Implementation Notes:
92 -- For insert, your business rules should be executed from this procedure and
93 -- should ideally (unless really necessary) just be straight procedure or
94 -- function calls. Try and avoid using conditional branching logic.
95 --
96 -- Access Status:
97 -- Internal Row Handler Use Only.
98 --
99 -- {End of comments}
100 -- ----------------------------------------------------------------------------
101 Procedure insert_validate
102 (p_effective_date in date
103 ,p_rec in per_rol_shd.g_rec_type
104 );
105 --
106 -- ----------------------------------------------------------------------------
107 -- |---------------------------< update_validate >----------------------------|
108 -- ----------------------------------------------------------------------------
109 -- {Start Of Comments}
110 --
111 -- Description:
112 -- This procedure controls the execution of all update business rules
113 -- validation.
114 --
115 -- Prerequisites:
116 -- This private procedure is called from upd procedure.
117 --
118 -- In Parameters:
119 -- A Pl/Sql record structure.
120 --
121 -- Post Success:
122 -- Processing continues.
123 --
124 -- Post Failure:
125 -- If a business rules fails the error will not be handled by this procedure
126 -- unless explicity coded.
127 --
128 -- Developer Implementation Notes:
129 -- For update, your business rules should be executed from this procedure and
130 -- should ideally (unless really necessary) just be straight procedure or
131 -- function calls. Try and avoid using conditional branching logic.
132 --
133 -- Access Status:
134 -- Internal Row Handler Use Only.
135 --
136 -- {End Of Comments}
137 -- ----------------------------------------------------------------------------
138 Procedure update_validate
139 (p_effective_date in date
140 ,p_rec in per_rol_shd.g_rec_type
141 );
142 --
143 -- ----------------------------------------------------------------------------
144 -- |---------------------------< delete_validate >----------------------------|
145 -- ----------------------------------------------------------------------------
146 -- {Start Of Comments}
147 --
148 -- Description:
149 -- This procedure controls the execution of all delete business rules
150 -- validation.
151 --
152 -- Prerequisites:
153 -- This private procedure is called from del procedure.
154 --
155 -- In Parameters:
156 -- A Pl/Sql record structure.
157 --
158 -- Post Success:
159 -- Processing continues.
160 --
161 -- Post Failure:
162 -- If a business rules fails the error will not be handled by this procedure
163 -- unless explicity coded.
164 --
165 -- Developer Implementation Notes:
166 -- For delete, your business rules should be executed from this procedure and
167 -- should ideally (unless really necessary) just be straight procedure or
168 -- function calls. Try and avoid using conditional branching logic.
169 --
170 -- Access Status:
171 -- Internal Row Handler Use Only.
172 --
173 --
174 -- ----------------------------------------------------------------------------
175 Procedure delete_validate
176 (p_rec in per_rol_shd.g_rec_type
177 );
178 --
179 -- ----------------------------------------------------------------------------
180 -- |-----------------------------< chk_dates >--------------------------------|
181 -- ----------------------------------------------------------------------------
182 --
183 -- Description:
184 -- Validates that the end_date is later than the start_date
185 --
186 -- Pre-Requisites:
187 -- None.
188 --
189 -- In Parameters:
190 -- p_start_date
191 -- p_end_date
192 -- p_role_id
193 --
194 -- Post Success:
195 -- Processing continues if end_date is later than start_date.
196 --
197 -- Post Failure:
198 -- An application error is raised and processing is terminated if
199 -- end_date is invalid.
200 --
201 -- Access Status:
202 -- Internal Development use only.
203 --
204 -- -------------------------------------------------------------------
205 procedure chk_dates
206 (p_start_date in date
207 ,p_end_date in date
208 );
209
210 -- Start of fix 2497485
211 -- ----------------------------------------------------------------------------
212 -- |---------------------------< chk_dup_roles >-------------------------------|
213 -- ----------------------------------------------------------------------------
214 --
215 -- Description:
216 -- This function will check for the duplicate roles.
217 --
218 -- Pre-Requisites:
219 -- None.
220 --
221 -- In Parameters:
222 -- p_person_id
223 -- p_job_group_id
224 -- p_job_id
225 --
226 -- Post Success:
227 -- A warning message will be shown to the user
228 --
229 -- Post Failure:
230 -- None
231 --
232 -- Access Status:
233 -- Internal Development use only.
234 --
235 -- -------------------------------------------------------------------
236 function chk_dup_roles
237 (p_person_id in per_roles.person_id%Type
238 ,p_job_group_id in per_roles.job_group_id%Type
239 ,p_job_id in per_roles.job_id%Type
240 ) return boolean;
241 -- End of 2497485
242 --
243 end per_rol_bus;
[Home] [Help]