1 PACKAGE per_jp_contact_extra_info AS
2 /* $Header: pejpreih.pkh 120.0 2005/05/31 10:57:17 appldev noship $ */
3 -- ----------------------------------------------------------------------------
4 -- |--------------------------< chk_information_type >------------------------|
5 -- ----------------------------------------------------------------------------
6 procedure chk_information_type(
7 p_contact_extra_info_id in number,
8 p_information_type in varchar2,
9 p_contact_relationship_id in number,
10 p_validation_start_date in date,
11 p_validation_end_date in date);
12 -- ----------------------------------------------------------------------------
13 -- |------------------------< chk_information_type_rkd >----------------------|
14 -- ----------------------------------------------------------------------------
15 procedure chk_information_type_rkd(
16 p_datetrack_mode in varchar2,
17 p_contact_extra_info_id in number,
18 p_information_type_o in varchar2,
19 p_contact_relationship_id_o in number,
20 p_validation_start_date in date,
21 p_validation_end_date in date);
22 /*
23 -- ----------------------------------------------------------------------------
24 -- |--------------------------< chk_information_type >------------------------|
25 -- ----------------------------------------------------------------------------
26 -- {Start Of Comments}
27 --
28 -- Description:
29 -- This procedure verifies information types that stores the same kind of
30 -- information are mutually exclusive on arbitorary date.
31 --
32 -- Prerequisites:
33 -- None.
34 --
35 -- In Parameters:
36 -- Name Reqd Type Description
37 -- p_effective_date Yes DATE Date the insert is effectively
38 -- made on. Used for validation
39 -- purpose.
40 -- p_contact_relationship_id Yes NUMBER Contact relationship for which
41 -- the extra info applies.
42 -- p_information_type Yes VARCHAR2 Information type the extra info
43 -- applies to.
44 --
45 -- Post Success:
46 -- Process continues.
47 --
48 -- Post Failure:
49 -- An application error will be raised and process is terminated.
50 --
51 -- Access Status:
52 -- Internal Table Handler Use Only.
53 --
54 -- {End Of Comments}
55 --
56 PROCEDURE chk_information_type(
57 p_effective_date DATE,
58 p_contact_relationship_id NUMBER,
59 p_information_type VARCHAR2);
60 --
61 -- ----------------------------------------------------------------------------
62 -- |----------------------------< chk_future_record >-------------------------|
63 -- ----------------------------------------------------------------------------
64 -- {Start Of Comments}
65 --
66 -- Description:
67 -- This procedure verifies information types that stores the same kind of
68 -- information are mutually exclusive on arbitorary date.
69 --
70 -- Prerequisites:
71 -- None.
72 --
73 -- In Parameters:
74 -- Name Reqd Type Description
75 -- p_effective_date Yes DATE Date the insert is effectively
76 -- made on. Used for validation
77 -- purpose.
78 -- p_contact_relationship_id Yes NUMBER Contact relationship for which
79 -- the extra info applies.
80 -- p_information_type Yes VARCHAR2 Information type the extra info
81 -- applies to.
82 --
83 -- Post Success:
84 -- Process continues.
85 --
86 -- Post Failure:
87 -- An application error will be raised and process is terminated.
88 --
89 -- Access Status:
90 -- Internal Table Handler Use Only.
91 --
92 -- {End Of Comments}
93 --
94 PROCEDURE chk_future_record(
95 p_effective_date DATE,
96 p_contact_relationship_id NUMBER,
97 p_information_type VARCHAR2);
98 --
99 -- ----------------------------------------------------------------------------
100 -- |--------------------< chk_future_record_before_del >----------------------|
101 -- ----------------------------------------------------------------------------
102 -- {Start Of Comments}
103 --
104 -- Description:
105 -- This procedure verifies information types that stores the same kind of
106 -- information are mutually exclusive on arbitorary date. This procedure
107 -- should be called before delete.
108 --
109 -- Prerequisites:
110 -- None.
111 --
112 -- In Parameters:
113 -- Name Reqd Type Description
114 -- p_effective_date Yes DATE Date the delete is effectively
115 -- made on. Used for validation
116 -- purpose.
117 -- p_contact_extra_info_id Yes NUMBER Contact extra info ID.
118 -- p_datetrack_delete_mode Yes VARCHAR2 DateTrack mode the delete uses.
119 --
120 -- Post Success:
121 -- Process continues.
122 --
123 -- Post Failure:
124 -- An application error will be raised and process is terminated.
125 --
126 -- Access Status:
127 -- Internal Table Handler Use Only.
128 --
129 -- {End Of Comments}
130 --
131 PROCEDURE chk_future_record_before_del(
132 p_effective_date DATE,
133 p_contact_extra_info_id NUMBER,
134 p_datetrack_delete_mode VARCHAR2);
135 --
136 -- ----------------------------------------------------------------------------
137 -- |----------------------------< chk_si_itax_flag >--------------------------|
138 -- ----------------------------------------------------------------------------
139 -- {Start Of Comments}
140 --
141 -- Description:
142 -- This procedure verifies si_itax_flag of the parent relationship is set to
143 -- 'Y'.
144 --
145 -- Prerequisites:
146 -- None.
147 --
148 -- In Parameters:
149 -- Name Reqd Type Description
150 -- p_contact_relationship_id Yes NUMBER Contact relationship for which
151 -- the extra info applies.
152 --
153 -- Post Success:
154 -- Process continues.
155 --
156 -- Post Failure:
157 -- An application error will be raised and process is terminated.
158 --
159 -- Access Status:
160 -- Internal Table Handler Use Only.
161 --
162 -- {End Of Comments}
163 --
164 PROCEDURE chk_si_itax_flag(
165 p_contact_relationship_id NUMBER);
166 --
167 -- ----------------------------------------------------------------------------
168 -- |----------------------------< chk_aged_parent >---------------------------|
169 -- ----------------------------------------------------------------------------
170 -- {Start Of Comments}
171 --
172 -- Description:
173 -- This procedure verifies aged parent living with employee is over 70 years
174 -- old.
175 --
176 -- Prerequisites:
177 -- None.
178 --
179 -- In Parameters:
180 -- Name Reqd Type Description
181 -- p_effective_date Yes DATE Date the insert is
182 -- effectively made on. Used
183 -- for age culculation and
184 -- validation purpose.
185 -- p_contact_relationship_id Yes NUMBER Contact relationship for
186 -- which the extra info applies.
187 -- p_information_type Yes VARCHAR2 Information type the extra
188 -- info applies to.
189 -- p_cei_information1 Yes VARCHAR2 Entry value for aged parent
190 -- living with employee.
191 --
192 -- Post Success:
193 -- Process continues.
194 --
195 -- Post Failure:
196 -- An application error will be raised and process is terminated.
197 --
198 -- Access Status:
199 -- Internal Table Handler Use Only.
200 --
201 -- {End Of Comments}
202 --
203 PROCEDURE chk_aged_parent(
204 p_effective_date DATE,
205 p_contact_relationship_id NUMBER,
206 p_information_type VARCHAR2,
207 p_cei_information1 VARCHAR2);
208 --
209 -- ----------------------------------------------------------------------------
210 -- |-----------------------< chk_aged_parent_before_upd >---------------------|
211 -- ----------------------------------------------------------------------------
212 -- {Start Of Comments}
213 --
214 -- Description:
215 -- This procedure verifies aged parent living with employee is over 70 years
216 -- old and contact type is not spouse before update.
217 --
218 -- Prerequisites:
219 -- None.
220 --
221 -- In Parameters:
222 -- Name Reqd Type Description
223 -- p_effective_date Yes DATE Date the update is
224 -- effectively made on. Used
225 -- for age culculation and
226 -- validation purpose.
227 -- p_datetrack_update_mode Yes VARCHAR2 Datetrack update mode.
228 -- p_contact_relationship_id Yes NUMBER Contact relationship for
229 -- which the extra info applies.
230 -- p_information_type Yes VARCHAR2 Information type the extra
231 -- info applies to.
232 -- p_cei_information1 Yes VARCHAR2 Entry value for aged parent
233 -- living with employee.
234 --
235 -- Post Success:
236 -- Process continues.
237 --
238 -- Post Failure:
239 -- An application error will be raised and process is terminated.
240 --
241 -- Access Status:
242 -- Internal Table Handler Use Only.
243 --
244 -- {End Of Comments}
245 --
246 PROCEDURE chk_aged_parent_before_upd(
247 p_effective_date DATE,
248 p_datetrack_update_mode VARCHAR2,
249 p_contact_relationship_id NUMBER,
250 p_information_type VARCHAR2,
251 p_cei_information1 VARCHAR2);
252 --
253 */
254 END per_jp_contact_extra_info;
[Home] [Help]