1 Package per_rei_bus AUTHID CURRENT_USER as
2 /* $Header: pereirhi.pkh 120.0 2005/05/31 17:34:06 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_contact_extra_info_id
15 -- already exists.
16 --
17 -- In Arguments:
18 -- p_contact_relationship_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 if the value does not exist.
25 --
26 -- Access Status:
27 -- Internal Development Use Only.
28 --
29 -- {End Of Comments}
30 -- ---------------------------------------------------------------------------
31 procedure set_security_group_id
32 (p_contact_relationship_id in number
33 ,p_associated_column1 in varchar2 default null
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_contact_extra_info_id
47 -- already exists.
48 --
49 -- In Arguments:
50 -- p_contact_extra_info_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_contact_extra_info_id in number
66 ) RETURN varchar2;
67 --
68 -- ----------------------------------------------------------------------------
69 -- |---------------------< chk_contact_relationship_id >----------------------|
70 -- ----------------------------------------------------------------------------
71 -- {Start Of Comments}
72 --
73 -- Description:
74 -- Verify that the value in p_contact_relationship_id is in the
75 -- per_contact_relationships table.
76 --
77 -- Pre Conditions:
78 -- None.
79 --
80 -- In Parameters:
81 -- Name Reqd Type Description
82 -- p_contact_relationship_id Yes NUMBER Contact Releationship ID.
83 --
84 -- Post Success:
85 -- Processing continues.
86 --
87 -- Post Failure:
88 -- An application error will be raised and processing is terminated.
89 --
90 -- Developer Implementation Notes:
91 -- None.
92 --
93 -- Access Status:
94 -- Internal Table Handler Use Only.
95 --
96 -- {End Of Comments}
97 -- ----------------------------------------------------------------------------
98 PROCEDURE chk_contact_relationship_id(
99 p_contact_relationship_id IN per_contact_extra_info_f.contact_relationship_id%TYPE);
100 --
101 -- ----------------------------------------------------------------------------
102 -- |-------------------------< chk_information_type >-------------------------|
103 -- ----------------------------------------------------------------------------
104 -- {Start Of Comments}
105 --
106 -- Description:
107 -- Validates that the contact information type exists in table
108 -- per_contact_info_types where active_inactive_flag is 'Y'.
109 --
110 -- Pre Conditions:
111 -- Data must be existed in table per_contact_info_types.
112 --
113 -- In Parameters:
114 -- Name Reqd Type Description
115 -- p_information_type Yes VARCHAR2 Contact Information Type
116 --
117 -- Post Success:
118 -- Processing continues.
119 --
120 -- Post Failure:
121 -- An application error will be raised and processing is terminated.
122 --
123 -- Developer Implementation Notes:
124 -- None.
125 --
126 -- Access Status:
127 -- Internal Table Handler Use Only.
128 --
129 -- {End Of Comments}
130 -- ----------------------------------------------------------------------------
131 procedure chk_information_type(
132 p_information_type in varchar2,
133 p_datetrack_mode in varchar2,
134 p_contact_relationship_id in number,
135 p_contact_extra_info_id in number,
136 p_validation_start_date in date,
137 p_validation_end_date in out nocopy date);
138 --
139 -- ----------------------------------------------------------------------------
140 -- |---------------------------< insert_validate >----------------------------|
141 -- ----------------------------------------------------------------------------
142 -- {Start Of Comments}
143 --
144 -- Description:
145 -- This procedure controls the execution of all insert business rules
146 -- validation.
147 --
148 -- Prerequisites:
149 -- This private procedure is called from ins procedure.
150 --
151 -- In Parameters:
152 -- A Pl/Sql record structre.
153 --
154 -- Post Success:
155 -- Processing continues.
156 --
157 -- Post Failure:
158 -- If a business rules fails the error will not be handled by this procedure
159 -- unless explicity coded.
160 --
161 -- Developer Implementation Notes:
162 -- For insert, your business rules should be executed from this procedure and
163 -- should ideally (unless really necessary) just be straight procedure or
164 -- function calls. Try and avoid using conditional branching logic.
165 --
166 -- Access Status:
167 -- Internal Row Handler Use Only.
168 --
169 -- {End Of Comments}
170 -- ----------------------------------------------------------------------------
171 Procedure insert_validate
172 (p_rec in per_rei_shd.g_rec_type
173 ,p_effective_date in date
174 ,p_datetrack_mode in varchar2
175 ,p_validation_start_date in date
176 ,p_validation_end_date in out nocopy date
177 );
178 --
179 -- ----------------------------------------------------------------------------
180 -- |---------------------------< update_validate >----------------------------|
181 -- ----------------------------------------------------------------------------
182 -- {Start Of Comments}
183 --
184 -- Description:
185 -- This procedure controls the execution of all update business rules
186 -- validation.
187 --
188 -- Prerequisites:
189 -- This private procedure is called from upd procedure.
190 --
191 -- In Parameters:
192 -- A Pl/Sql record structre.
193 --
194 -- Post Success:
195 -- Processing continues.
196 --
197 -- Post Failure:
198 -- If a business rules fails the error will not be handled by this procedure
199 -- unless explicity coded.
200 --
201 -- Developer Implementation Notes:
202 -- For update, your business rules should be executed from this procedure and
203 -- should ideally (unless really necessary) just be straight procedure or
204 -- function calls. Try and avoid using conditional branching logic.
205 --
206 -- Access Status:
207 -- Internal Row Handler Use Only.
208 --
209 -- {End Of Comments}
210 -- ----------------------------------------------------------------------------
211 Procedure update_validate
212 (p_rec in per_rei_shd.g_rec_type
213 ,p_effective_date in date
214 ,p_datetrack_mode in varchar2
215 ,p_validation_start_date in date
216 ,p_validation_end_date in date
217 );
218 --
219 -- ----------------------------------------------------------------------------
220 -- |---------------------------< delete_validate >----------------------------|
221 -- ----------------------------------------------------------------------------
222 -- {Start Of Comments}
223 --
224 -- Description:
225 -- This procedure controls the execution of all delete business rules
226 -- validation.
227 --
228 -- Prerequisites:
229 -- This private procedure is called from del procedure.
230 --
231 -- In Parameters:
232 -- A Pl/Sql record structure.
233 --
234 -- Post Success:
235 -- Processing continues.
236 --
237 -- Post Failure:
238 -- If a business rules fails the error will not be handled by this procedure
239 -- unless explicity coded.
240 --
241 -- Developer Implementation Notes:
242 -- For delete, your business rules should be executed from this procedure and
243 -- should ideally (unless really necessary) just be straight procedure or
244 -- function calls. Try and avoid using conditional branching logic.
245 --
246 -- Access Status:
247 -- Internal Row Handler Use Only.
248 --
249 -- {End Of Comments}
250 -- ----------------------------------------------------------------------------
251 Procedure delete_validate
252 (p_rec in per_rei_shd.g_rec_type
253 ,p_effective_date in date
254 ,p_datetrack_mode in varchar2
255 ,p_validation_start_date in date
256 ,p_validation_end_date in out nocopy date
257 );
258 --
259 end per_rei_bus;
[Home] [Help]