1 Package ota_rud_bus AUTHID CURRENT_USER as
2 /* $Header: otrudrhi.pkh 120.0 2005/05/29 07:32:29 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_resource_usage_id
15 -- already exists.
16 --
17 -- In Arguments:
18 -- p_resource_usage_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_resource_usage_id in number
34 ,p_associated_column1 in varchar2 default null
35 );
36 --
37 -- ----------------------------------------------------------------------------
38 -- |--------------------------< check_unique_key >--------------------------|
39 -- ----------------------------------------------------------------------------
40 --
41 -- A specific resource cannot be entered against the same course
42 -- more than once.
43 --
44 procedure check_unique_key
45 (
46 p_supplied_resource_id in number,
47 p_offering_id in number
48 );
49 --
50 -- ----------------------------------------------------------------------------
51 -- |------------------------------< check_off >-------------------------------|
52 -- ----------------------------------------------------------------------------
53 --
54 procedure check_off (
55 p_offering_id in number,
56 p_start_date in date,
57 p_end_date in date
58 );
59 --
60 -- ----------------------------------------------------------------------------
61 -- |------------------------------< check_tsr >-------------------------------|
62 -- ----------------------------------------------------------------------------
63
64 --
65 procedure check_tsr (
66 p_supplied_resource_id in number,
67 p_start_date in date,
68 p_end_date in date
69 );
70 --
71 --
72 -- ---------------------------------------------------------------------------
73 -- |---------------------< return_legislation_code >-------------------------|
74 -- ---------------------------------------------------------------------------
75 -- {Start Of Comments}
76 --
77 -- Description:
78 -- Return the legislation code for a specific primary key value
79 --
80 -- Prerequisites:
81 -- The primary key identified by p_resource_usage_id
82 -- already exists.
83 --
84 -- In Arguments:
85 -- p_resource_usage_id
86 --
87 --
88 -- Post Success:
89 -- The business group's legislation code will be returned.
90 --
91 -- Post Failure:
92 -- An error is raised if the value does not exist.
93 --
94 -- Access Status:
95 -- Internal Development Use Only.
96 --
97 -- {End Of Comments}
98 -- ---------------------------------------------------------------------------
99 FUNCTION return_legislation_code
100 (p_resource_usage_id in number
101 ) RETURN varchar2;
102 --
103 --
104 -- ----------------------------------------------------------------------------
105 -- |---------------------------< insert_validate >----------------------------|
106 -- ----------------------------------------------------------------------------
107 -- {Start of comments}
108 --
109 -- Description:
110 -- This procedure controls the execution of all insert business rules
111 -- validation.
112 --
113 -- Prerequisites:
114 -- This private procedure is called from ins procedure.
115 --
116 -- In Parameters:
117 -- A Pl/Sql record structure.
118 --
119 -- Post Success:
120 -- Processing continues.
121 --
122 -- Post Failure:
123 -- If a business rules fails the error will not be handled by this procedure
124 -- unless explicity coded.
125 --
126 -- Developer Implementation Notes:
127 -- For insert, your business rules should be executed from this procedure
128 -- and should ideally (unless really necessary) just be straight procedure
129 -- or function calls. Try and avoid using conditional branching logic.
130 --
131 -- Access Status:
132 -- Internal Row Handler Use Only.
133 --
134 -- {End of comments}
135 -- ----------------------------------------------------------------------------
136 Procedure insert_validate
137 (p_effective_date in date
138 ,p_rec in ota_rud_shd.g_rec_type
139 );
140 --
141 -- ----------------------------------------------------------------------------
142 -- |---------------------------< update_validate >----------------------------|
143 -- ----------------------------------------------------------------------------
144 -- {Start Of Comments}
145 --
146 -- Description:
147 -- This procedure controls the execution of all update business rules
148 -- validation.
149 --
150 -- Prerequisites:
151 -- This private procedure is called from upd procedure.
152 --
153 -- In Parameters:
154 -- A Pl/Sql record structure.
155 --
156 -- Post Success:
157 -- Processing continues.
158 --
159 -- Post Failure:
160 -- If a business rules fails the error will not be handled by this procedure
161 -- unless explicity coded.
162 --
163 -- Access Status:
164 -- Internal Row Handler Use Only.
165 --
166 -- {End Of Comments}
167 -- ----------------------------------------------------------------------------
168 Procedure update_validate
169 (p_effective_date in date
170 ,p_rec in ota_rud_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
197 -- and should ideally (unless really necessary) just be straight procedure
198 -- or function calls. Try and avoid using conditional branching logic.
199 --
200 -- Access Status:
201 -- Internal Row Handler Use Only.
202 --
203 -- {End Of Comments}
204 -- ----------------------------------------------------------------------------
205 Procedure delete_validate
206 (p_rec in ota_rud_shd.g_rec_type
207 );
208
209 --
210 end ota_rud_bus;
[Home] [Help]