1 Package hr_tim_bus as
2 /* $Header: hrtimrhi.pkh 120.0 2005/05/31 03:14:53 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 -- No business group context. Security group not applicable.
13 --
14 -- Prerequisites:
15 -- The primary key identified by p_template_item_id already exists.
16 --
17 -- In Arguments:
18 -- p_template_item_id
19 --
20 -- Post Success:
21 -- The security_group_id will be set in CLIENT_INFO.
22 --
23 -- Post Failure:
24 -- An error is raised.
25 --
26 -- Access Status:
27 -- Internal Development Use Only.
28 --
29 -- {End Of Comments}
30 -- ---------------------------------------------------------------------------
31 procedure set_security_group_id
32 (p_template_item_id in number
33 );
34 --
35 --
36 -- ---------------------------------------------------------------------------
37 -- |---------------------< return_legislation_code >-------------------------|
38 -- ---------------------------------------------------------------------------
39 -- {Start Of Comments}
40 --
41 -- Description:
42 -- Return the legislation code for a specific primary key value. This may
43 -- be null in certain cases.
44 --
45 -- Prerequisites:
46 -- The primary key identified by p_template_item_id already exists.
47 --
48 -- In Arguments:
49 -- p_template_item_id
50 --
51 -- Post Success:
52 -- The business group's legislation code will be returned.
53 --
54 -- Post Failure:
55 -- An error is raised.
56 --
57 -- Access Status:
58 -- Internal Development Use Only.
59 --
60 -- {End Of Comments}
61 -- ---------------------------------------------------------------------------
62 FUNCTION return_legislation_code
63 (p_template_item_id in number
64 ) RETURN varchar2;
65 --
66 --
67 -- ---------------------------------------------------------------------------
68 -- |---------------------< chk_no_flex_segment_comb >------------------------|
69 -- ---------------------------------------------------------------------------
70 -- {Start Of Comments}
71 --
72 -- Description:
73 -- Called from post_insert to ensure that template does not contain popup and
74 -- segments from the same flexfield.
75 --
76 -- Prerequisites:
77 -- The primary key identified by p_form_item_id must already exist.
78 --
79 -- In Arguments:
80 -- p_form_template_id
81 -- p_object_version_number
82 -- p_form_item_id
83 --
84 -- Post Success:
85 -- Processing continues.
86 --
87 -- Post Failure:
88 -- An error is raised.
89 --
90 -- Access Status:
91 -- Internal Development Use Only.
92 --
93 -- {End Of Comments}
94 -- ---------------------------------------------------------------------------
95 PROCEDURE chk_no_flex_segment_comb
96 (p_form_template_id in number
97 ,p_object_version_number in number
98 ,p_form_item_id in number
99 );
100 --
101 -- ----------------------------------------------------------------------------
102 -- |---------------------------< insert_validate >----------------------------|
103 -- ----------------------------------------------------------------------------
104 -- {Start of comments}
105 --
106 -- Description:
107 -- This procedure controls the execution of all insert business rules
108 -- validation.
109 --
110 -- Prerequisites:
111 -- This private procedure is called from ins procedure.
112 --
113 -- In Parameters:
114 -- A Pl/Sql record structure.
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 insert, 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 insert_validate
134 (p_rec in hr_tim_shd.g_rec_type
135 );
136 --
137 -- ----------------------------------------------------------------------------
138 -- |---------------------------< update_validate >----------------------------|
139 -- ----------------------------------------------------------------------------
140 -- {Start Of Comments}
141 --
142 -- Description:
143 -- This procedure controls the execution of all update business rules
144 -- validation.
145 --
146 -- Prerequisites:
147 -- This private procedure is called from upd procedure.
148 --
149 -- In Parameters:
150 -- A Pl/Sql record structure.
151 --
152 -- Post Success:
153 -- Processing continues.
154 --
155 -- Post Failure:
156 -- If a business rules fails the error will not be handled by this procedure
157 -- unless explicity coded.
158 --
159 -- Developer Implementation Notes:
160 -- For update, your business rules should be executed from this procedure and
161 -- should ideally (unless really necessary) just be straight procedure or
162 -- function calls. Try and avoid using conditional branching logic.
163 --
164 -- Access Status:
165 -- Internal Row Handler Use Only.
166 --
167 -- {End Of Comments}
168 -- ----------------------------------------------------------------------------
169 Procedure update_validate
170 (p_rec in hr_tim_shd.g_rec_type
171 );
172 --
173 -- ----------------------------------------------------------------------------
174 -- |---------------------------< delete_validate >----------------------------|
175 -- ----------------------------------------------------------------------------
176 -- {Start Of Comments}
177 --
178 -- Description:
179 -- This procedure controls the execution of all delete business rules
180 -- validation.
181 --
182 -- Prerequisites:
183 -- This private procedure is called from del procedure.
184 --
185 -- In Parameters:
186 -- A Pl/Sql record structure.
187 --
188 -- Post Success:
189 -- Processing continues.
190 --
191 -- Post Failure:
192 -- If a business rules fails the error will not be handled by this procedure
193 -- unless explicity coded.
194 --
195 -- Developer Implementation Notes:
196 -- For delete, your business rules should be executed from this procedure and
197 -- should ideally (unless really necessary) just be straight procedure or
198 -- function calls. Try and avoid using conditional branching logic.
199 --
200 -- Access Status:
201 -- Internal Row Handler Use Only.
202 --
203 --
204 -- ----------------------------------------------------------------------------
205 Procedure delete_validate
206 (p_rec in hr_tim_shd.g_rec_type
207 );
208 --
209 end hr_tim_bus;
[Home] [Help]