1 Package pay_rtt_bus as
2 /* $Header: pyrttrhi.pkh 120.0 2005/05/29 08:28:04 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_run_type_id
15 -- already exists.
16 --
17 -- In Arguments:
18 -- p_run_type_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_run_type_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_run_type_id
47 -- already exists.
48 --
49 -- In Arguments:
50 -- p_run_type_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_run_type_id in number
66 ,p_language in varchar2
67 ) RETURN varchar2;
68 --
69 --
70 -- ----------------------------------------------------------------------------
71 -- |--------------------------< chk_run_type_id >-----------------------------|
72 -- ----------------------------------------------------------------------------
73 -- {Start Of Comments}
74 --
75 -- Description:
76 -- The surrogate key, run_type_id must exist on the non-translated table
77 -- pay_run_types_f.
78 --
79 -- Pre Conditions:
80 -- g_old_rec has been populated with details of the values currently in
81 -- the database.
82 --
83 -- In Arguments:
84 -- p_rec has been populated with the updated values the user would like the
85 -- record set to.
86 --
87 -- Post Success:
88 -- Processing continues if the run_type_id exist on the non-translated table
89 -- pay_run_types_f.
90 --
91 -- Post Failure:
92 -- An application error is raised if run_type_id does not exist on
93 -- pay_run_types_f.
94 --
95 -- {End Of Comments}
96 -- ----------------------------------------------------------------------------
97 Procedure chk_run_type_id
98 (p_run_type_id in number);
99 -- ----------------------------------------------------------------------------
100 -- |------------------------< chk_tl_run_type_name >--------------------------|
101 -- ----------------------------------------------------------------------------
102 -- {Start Of Comments}
103 --
104 -- Description:
105 -- The run_type_name must be unique within a language
106 --
107 -- Pre Conditions:
108 -- g_old_rec has been populated with details of the values currently in
109 -- the database.
110 --
111 -- In Arguments:
112 -- p_rec has been populated with the updated values the user would like the
113 -- record set to.
114 --
115 -- Post Success:
116 -- Processing continues if the run_type_id exist on the non-translated table
117 -- pay_run_types_f.
118 --
119 -- Post Failure:
120 -- An application error is raised if run_type_id does not exist on
121 -- pay_run_types_f.
122 --
123 -- {End Of Comments}
124 -- ----------------------------------------------------------------------------
125 Procedure chk_tl_run_type_name
126 (p_run_type_id in number
127 ,p_language in varchar2
128 ,p_run_type_name in varchar2);
129 -- ----------------------------------------------------------------------------
130 -- |---------------------------< insert_validate >----------------------------|
131 -- ----------------------------------------------------------------------------
132 -- {Start of comments}
133 --
134 -- Description:
135 -- This procedure controls the execution of all insert business rules
136 -- validation.
137 --
138 -- Prerequisites:
139 -- This private procedure is called from ins procedure.
140 --
141 -- In Parameters:
142 -- A Pl/Sql record structure.
143 --
144 -- Post Success:
145 -- Processing continues.
146 --
147 -- Post Failure:
148 -- If a business rules fails the error will not be handled by this procedure
149 -- unless explicity coded.
150 --
151 -- Developer Implementation Notes:
152 -- For insert, your business rules should be executed from this procedure and
153 -- should ideally (unless really necessary) just be straight procedure or
154 -- function calls. Try and avoid using conditional branching logic.
155 --
156 -- Access Status:
157 -- Internal Row Handler Use Only.
158 --
159 -- {End of comments}
160 -- ----------------------------------------------------------------------------
161 Procedure insert_validate
162 (p_rec in pay_rtt_shd.g_rec_type
163 ,p_run_type_id in number
164 );
165 --
166 -- ----------------------------------------------------------------------------
167 -- |---------------------------< update_validate >----------------------------|
168 -- ----------------------------------------------------------------------------
169 -- {Start Of Comments}
170 --
171 -- Description:
172 -- This procedure controls the execution of all update business rules
173 -- validation.
174 --
175 -- Prerequisites:
176 -- This private procedure is called from upd procedure.
177 --
178 -- In Parameters:
179 -- A Pl/Sql record structure.
180 --
181 -- Post Success:
182 -- Processing continues.
183 --
184 -- Post Failure:
185 -- If a business rules fails the error will not be handled by this procedure
186 -- unless explicity coded.
187 --
188 -- Developer Implementation Notes:
189 -- For update, your business rules should be executed from this procedure and
190 -- should ideally (unless really necessary) just be straight procedure or
191 -- function calls. Try and avoid using conditional branching logic.
192 --
193 -- Access Status:
194 -- Internal Row Handler Use Only.
195 --
196 -- {End Of Comments}
197 -- ----------------------------------------------------------------------------
198 Procedure update_validate
199 (p_rec in pay_rtt_shd.g_rec_type
200 );
201 --
202 -- ----------------------------------------------------------------------------
203 -- |---------------------------< delete_validate >----------------------------|
204 -- ----------------------------------------------------------------------------
205 -- {Start Of Comments}
206 --
207 -- Description:
208 -- This procedure controls the execution of all delete business rules
209 -- validation.
210 --
211 -- Prerequisites:
212 -- This private procedure is called from del procedure.
213 --
214 -- In Parameters:
215 -- A Pl/Sql record structure.
216 --
217 -- Post Success:
218 -- Processing continues.
219 --
220 -- Post Failure:
221 -- If a business rules fails the error will not be handled by this procedure
222 -- unless explicity coded.
223 --
224 -- Developer Implementation Notes:
225 -- For delete, your business rules should be executed from this procedure and
226 -- should ideally (unless really necessary) just be straight procedure or
227 -- function calls. Try and avoid using conditional branching logic.
228 --
229 -- Access Status:
230 -- Internal Row Handler Use Only.
231 --
232 -- {End Of Comments}
233 -- ----------------------------------------------------------------------------
234 Procedure delete_validate
235 (p_rec in pay_rtt_shd.g_rec_type
236 );
237 --
238 end pay_rtt_bus;
[Home] [Help]