1 Package hr_qsf_bus as
2 /* $Header: hrqsfrhi.pkh 120.0 2005/05/31 02:27:54 appldev noship $ */
3 --
4 -- ----------------------------------------------------------------------------
5 -- |-------------------< chk_questionnaire_template_id >----------------------|
6 -- ----------------------------------------------------------------------------
7 --
8 -- Description:
9 -- Checks that the questionnaire_template_id exists in the
10 -- HR_QUESTIONNAIRES table.
11 --
12 -- Pre-requisites:
13 -- None.
14 --
15 -- IN Parameters:
16 -- p_questionnaire_template_id
17 --
18 -- Post Success:
19 -- Processing continues if the questionnaire_template_id is valid.
20 --
21 -- Post Failure:
22 -- An application error is raised and processing terminates if the
23 -- questionnaire_template_id is invalid.
24 --
25 -- Developer/Implementation Notes:
26 -- None.
27 --
28 -- Access Status:
29 -- Internal Development Use Only.
30 -- ----------------------------------------------------------------------------
31 --
32 Procedure chk_questionnaire_template_id
33 (p_questionnaire_template_id
34 in hr_quest_fields.questionnaire_template_id%TYPE
35 );
36 --
37 --
38 -- ----------------------------------------------------------------------------
39 -- |----------------------------< chk_name >----------------------------------|
40 -- ----------------------------------------------------------------------------
41 --
42 -- Description:
43 -- Checks that the name is not null.
44 --
45 -- Pre-requisites:
46 -- None.
47 --
48 -- IN Parameters:
49 -- p_name
50 --
51 -- Post Success:
52 -- If the name is valid, processing continues.
53 --
54 -- Post Failure:
55 -- An application error is raised, and processing is terminated if the
56 -- name is invalid.
57 --
58 -- Developer/Implementation notes:
59 -- None.
60 --
61 -- Access Status:
62 -- Internal Development Use Only.
63 -- ---------------------------------------------------------------------------
64 --
65 Procedure chk_name
66 (p_name in hr_quest_fields.name%TYPE
67 );
68 --
69 -- ---------------------------------------------------------------------------
70 -- |----------------------< chk_html_text >----------------------------------|
71 -- ---------------------------------------------------------------------------
72 --
73 -- Description:
74 -- Validates that html_text is not null, and that its size is less than
75 -- 27K.
76 --
77 -- Pre-requisites:
78 -- None.
79 --
80 -- IN Parameters:
81 -- p_html_text
82 --
83 -- Post Success:
84 -- Processing continues if the html_text is valid.
85 --
86 -- Post Failure:
87 -- An application error is raised, and processing is terminated if the
88 -- html_text is invalid.
89 --
90 -- Developer/Implementation Notes:
91 -- None.
92 --
93 -- Access Status:
94 -- Internal Development Use Only.
95 -- ----------------------------------------------------------------------------
96 --
97 Procedure chk_html_text
98 (p_html_text in hr_quest_fields.html_text%TYPE
99 );
100 --
101 -- ---------------------------------------------------------------------------
102 -- |-----------------------------< chk_type >--------------------------------|
103 -- ---------------------------------------------------------------------------
104 --
105 -- Description:
106 -- Checks that the TYPE exists in HR_LOOKUPS, where the lookup_type is
107 -- 'QUEST_FIELD_TYPE'.
108 --
109 -- Pre-requisites:
110 -- None.
111 --
112 -- IN Parameters:
113 -- p_type
114 -- p_effective_date
115 --
116 -- Post Success:
117 -- Processing continues if the type is found to be valid.
118 --
119 -- Post Failure:
120 -- An application error is raised and processing is terminated if the
121 -- type is invalid.
122 --
123 -- Developer/Implementation Notes:
124 -- This chk_ procedure should be available from a direct call.
125 --
126 -- Access Status:
127 -- Internal Development Use Only.
128 --
129 Procedure chk_type
130 (p_type in hr_quest_fields.type%TYPE
131 ,p_effective_date in date
132 );
133 --
134 --
135 -- ----------------------------------------------------------------------------
136 -- |------------------------< chk_sql_required_flag >-------------------------|
137 -- ----------------------------------------------------------------------------
138 --
139 -- Description:
140 -- Checks that sql_required_flag is not null, and exists in HR_LOOKUPS,
141 -- where the lookup_code is 'YES_NO'.
142 --
143 -- Pre-requisites:
144 -- None.
145 --
146 -- IN Parameters:
147 -- p_sql_required_flag
148 -- p_effective_date
149 --
150 -- Post Success:
151 -- Processing continues if the sql_required_flag is valid.
152 --
153 -- Post Failure:
154 -- An application error is raised, and processing is terminated if
155 -- sql_required_flag is invalid.
156 --
157 -- Developer/Implementation Notes:
158 -- Can be called as a direct call from Forms.
159 --
160 -- Access Status:
161 -- Internal Development Use Only.
162 --
163 --
164 Procedure chk_sql_required_flag
165 (p_sql_required_flag in hr_quest_fields.sql_required_flag%TYPE
166 ,p_effective_date in date
167 );
168
169 --
170 -- ----------------------------------------------------------------------------
171 -- |---------------------------< insert_validate >----------------------------|
172 -- ----------------------------------------------------------------------------
173 -- {Start Of Comments}
174 --
175 -- Description:
176 -- This procedure controls the execution of all insert business rules
177 -- validation.
178 --
179 -- Prerequisites:
180 -- This private procedure is called from ins procedure.
181 --
182 -- In Parameters:
183 -- A Pl/Sql record structre.
184 --
185 -- Post Success:
186 -- Processing continues.
187 --
188 -- Post Failure:
189 -- If a business rules fails the error will not be handled by this procedure
190 -- unless explicity coded.
191 --
192 -- Developer Implementation Notes:
193 -- For insert, your business rules should be executed from this procedure and
194 -- should ideally (unless really necessary) just be straight procedure or
195 -- function calls. Try and avoid using conditional branching logic.
196 --
197 -- Access Status:
198 -- Internal Row Handler Use Only.
199 --
200 -- {End Of Comments}
201 -- ----------------------------------------------------------------------------
202 Procedure insert_validate(p_rec in hr_qsf_shd.g_rec_type,
203 p_effective_date in date);
204 --
205 -- ----------------------------------------------------------------------------
206 -- |---------------------------< update_validate >----------------------------|
207 -- ----------------------------------------------------------------------------
208 -- {Start Of Comments}
209 --
210 -- Description:
211 -- This procedure controls the execution of all update business rules
212 -- validation.
213 --
214 -- Prerequisites:
215 -- This private procedure is called from upd procedure.
216 --
217 -- In Parameters:
218 -- A Pl/Sql record structre.
219 --
220 -- Post Success:
221 -- Processing continues.
222 --
223 -- Post Failure:
224 -- If a business rules fails the error will not be handled by this procedure
225 -- unless explicity coded.
226 --
227 -- Developer Implementation Notes:
228 -- For update, your business rules should be executed from this procedure and
229 -- should ideally (unless really necessary) just be straight procedure or
230 -- function calls. Try and avoid using conditional branching logic.
231 --
232 -- Access Status:
233 -- Internal Row Handler Use Only.
234 --
235 -- {End Of Comments}
236 -- ----------------------------------------------------------------------------
237 Procedure update_validate(p_rec in hr_qsf_shd.g_rec_type,
238 p_effective_date in date);
239 --
240 -- ----------------------------------------------------------------------------
241 -- |---------------------------< delete_validate >----------------------------|
242 -- ----------------------------------------------------------------------------
243 -- {Start Of Comments}
244 --
245 -- Description:
246 -- This procedure controls the execution of all delete business rules
247 -- validation.
248 --
249 -- Prerequisites:
250 -- This private procedure is called from del procedure.
251 --
252 -- In Parameters:
253 -- A Pl/Sql record structre.
254 --
255 -- Post Success:
256 -- Processing continues.
257 --
258 -- Post Failure:
259 -- If a business rules fails the error will not be handled by this procedure
260 -- unless explicity coded.
261 --
262 -- Developer Implementation Notes:
263 -- For delete, your business rules should be executed from this procedure and
264 -- should ideally (unless really necessary) just be straight procedure or
265 -- function calls. Try and avoid using conditional branching logic.
266 --
267 -- Access Status:
268 -- Internal Row Handler Use Only.
269 --
270 -- {End Of Comments}
271 -- ----------------------------------------------------------------------------
272 Procedure delete_validate(p_rec in hr_qsf_shd.g_rec_type);
273 --
274 end hr_qsf_bus;
[Home] [Help]