1 Package hr_itp_bus as
2 /* $Header: hritprhi.pkh 120.0 2005/05/31 01:00:40 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_item_property_id already exists.
16 --
17 -- In Arguments:
18 -- p_item_property_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_item_property_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_item_property_id already exists.
47 --
48 -- In Arguments:
49 -- p_item_property_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_item_property_id in number
64 ) RETURN varchar2;
65 --
66 -- ---------------------------------------------------------------------------
67 -- |---------------------------< return_item_type >--------------------------|
68 -- ---------------------------------------------------------------------------
69 -- {Start Of Comments}
70 --
71 -- Description:
72 -- Return the item type for a specific unique key value.
73 --
74 -- Prerequisites:
75 -- None
76 --
77 -- In Arguments:
78 -- p_form_item_id
79 -- p_template_item_id
80 -- p_template_item_context_id
81 --
82 -- Post Success:
83 -- The item type will be returned.
84 --
85 -- Post Failure:
86 -- An error is raised.
87 --
88 -- Access Status:
89 -- Internal Development Use Only.
90 --
91 -- {End Of Comments}
92 -- ---------------------------------------------------------------------------
93 FUNCTION return_item_type
94 (p_form_item_id in number default hr_api.g_number
95 ,p_template_item_id in number default hr_api.g_number
96 ,p_template_item_context_id in number default hr_api.g_number
97 ) RETURN varchar2;
98 --
99 --
100 -- ----------------------------------------------------------------------------
101 -- |---------------------------< insert_validate >----------------------------|
102 -- ----------------------------------------------------------------------------
103 -- {Start of comments}
104 --
105 -- Description:
106 -- This procedure controls the execution of all insert business rules
107 -- validation.
108 --
109 -- Prerequisites:
110 -- This private procedure is called from ins procedure.
111 --
112 -- In Parameters:
113 -- A Pl/Sql record structure.
114 --
115 -- Post Success:
116 -- Processing continues.
117 --
118 -- Post Failure:
119 -- If a business rules fails the error will not be handled by this procedure
120 -- unless explicity coded.
121 --
122 -- Developer Implementation Notes:
123 -- For insert, your business rules should be executed from this procedure and
124 -- should ideally (unless really necessary) just be straight procedure or
125 -- function calls. Try and avoid using conditional branching logic.
126 --
127 -- Access Status:
128 -- Internal Row Handler Use Only.
129 --
130 -- {End of comments}
131 -- ----------------------------------------------------------------------------
132 Procedure insert_validate
133 (p_effective_date in date
134 ,p_rec in hr_itp_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_effective_date in date
171 ,p_rec in hr_itp_shd.g_rec_type
172 );
173 --
174 -- ----------------------------------------------------------------------------
175 -- |---------------------------< delete_validate >----------------------------|
176 -- ----------------------------------------------------------------------------
177 -- {Start Of Comments}
178 --
179 -- Description:
180 -- This procedure controls the execution of all delete business rules
181 -- validation.
182 --
183 -- Prerequisites:
184 -- This private procedure is called from del procedure.
185 --
186 -- In Parameters:
187 -- A Pl/Sql record structure.
188 --
189 -- Post Success:
190 -- Processing continues.
191 --
192 -- Post Failure:
193 -- If a business rules fails the error will not be handled by this procedure
194 -- unless explicity coded.
195 --
196 -- Developer Implementation Notes:
197 -- For delete, your business rules should be executed from this procedure and
198 -- should ideally (unless really necessary) just be straight procedure or
199 -- function calls. Try and avoid using conditional branching logic.
200 --
201 -- Access Status:
202 -- Internal Row Handler Use Only.
203 --
204 --
205 -- ----------------------------------------------------------------------------
206 Procedure delete_validate
207 (p_rec in hr_itp_shd.g_rec_type
208 );
209 --
210 end hr_itp_bus;
[Home] [Help]