1 Package irc_ipd_shd as
2 /* $Header: iripdrhi.pkh 120.0 2005/07/26 15:09:47 mbocutt noship $ */
3 --
4 -- ----------------------------------------------------------------------------
5 -- | Global Record Type Specification |
6 -- ----------------------------------------------------------------------------
7 --
8 Type g_rec_type Is Record
9 (pending_data_id number(15)
10 ,email_address varchar2(100)
11 ,vacancy_id number(15)
12 ,last_name varchar2(150)
13 ,first_name varchar2(150)
14 ,user_password varchar2(100)
15 ,resume_file_name varchar2(240)
16 ,resume_description varchar2(240)
17 ,resume_mime_type varchar2(30)
18 ,source_type varchar2(30)
19 ,job_post_source_name varchar2(240)
20 ,posting_content_id number(15)
21 ,person_id number(15)
22 ,processed varchar2(30)
23 ,sex varchar2(30)
24 ,date_of_birth date
25 ,per_information_category varchar2(30)
26 ,per_information1 varchar2(150)
27 ,per_information2 varchar2(150)
28 ,per_information3 varchar2(150)
29 ,per_information4 varchar2(150)
30 ,per_information5 varchar2(150)
31 ,per_information6 varchar2(150)
32 ,per_information7 varchar2(150)
33 ,per_information8 varchar2(150)
34 ,per_information9 varchar2(150)
35 ,per_information10 varchar2(150)
36 ,per_information11 varchar2(150)
37 ,per_information12 varchar2(150)
38 ,per_information13 varchar2(150)
39 ,per_information14 varchar2(150)
40 ,per_information15 varchar2(150)
41 ,per_information16 varchar2(150)
42 ,per_information17 varchar2(150)
43 ,per_information18 varchar2(150)
44 ,per_information19 varchar2(150)
45 ,per_information20 varchar2(150)
46 ,per_information21 varchar2(150)
47 ,per_information22 varchar2(150)
48 ,per_information23 varchar2(150)
49 ,per_information24 varchar2(150)
50 ,per_information25 varchar2(150)
51 ,per_information26 varchar2(150)
52 ,per_information27 varchar2(150)
53 ,per_information28 varchar2(150)
54 ,per_information29 varchar2(150)
55 ,per_information30 varchar2(150)
56 ,error_message varchar2(4000)
57 ,creation_date date
58 ,last_update_date date
59 ,allow_access varchar2(30)
60 ,user_guid raw(16)
61 ,visitor_resp_key varchar2(30)
62 ,visitor_resp_appl_id number(15)
63 ,security_group_key varchar2(30)
64 );
65 --
66 -- ----------------------------------------------------------------------------
67 -- | Global Definitions - Internal Development Use Only |
68 -- ----------------------------------------------------------------------------
69 --
70 g_old_rec g_rec_type; -- Global record definition
71 -- Global table name
72 g_tab_nam constant varchar2(30) := 'IRC_PENDING_DATA';
73 --
74 -- ----------------------------------------------------------------------------
75 -- |---------------------------< constraint_error >---------------------------|
76 -- ----------------------------------------------------------------------------
77 -- {Start Of Comments}
78 --
79 -- Description:
80 -- This procedure is called when a constraint has been violated (i.e.
81 -- The exception hr_api.check_integrity_violated,
82 -- hr_api.parent_integrity_violated, hr_api.child_integrity_violated or
83 -- hr_api.unique_integrity_violated has been raised).
84 -- The exceptions can only be raised as follows:
85 -- 1) A check constraint can only be violated during an INSERT or UPDATE
86 -- dml operation.
87 -- 2) A parent integrity constraint can only be violated during an
88 -- INSERT or UPDATE dml operation.
89 -- 3) A child integrity constraint can only be violated during an
90 -- DELETE dml operation.
91 -- 4) A unique integrity constraint can only be violated during INSERT or
92 -- UPDATE dml operation.
93 --
94 -- Prerequisites:
95 -- 1) Either hr_api.check_integrity_violated,
96 -- hr_api.parent_integrity_violated, hr_api.child_integrity_violated or
97 -- hr_api.unique_integrity_violated has been raised with the subsequent
98 -- stripping of the constraint name from the generated error message
99 -- text.
100 -- 2) Standalone validation test which corresponds with a constraint error.
101 --
102 -- In Parameter:
103 -- p_constraint_name is in upper format and is just the constraint name
104 -- (e.g. not prefixed by brackets, schema owner etc).
105 --
106 -- Post Success:
107 -- Development dependant.
108 --
109 -- Post Failure:
110 -- Developement dependant.
111 --
112 -- Developer Implementation Notes:
113 -- For each constraint being checked the hr system package failure message
114 -- has been generated as a template only. These system error messages should
115 -- be modified as required (i.e. change the system failure message to a user
116 -- friendly defined error message).
117 --
118 -- Access Status:
119 -- Internal Development Use Only.
120 --
121 -- {End Of Comments}
122 -- ----------------------------------------------------------------------------
123 Procedure constraint_error
124 (p_constraint_name in all_constraints.constraint_name%TYPE);
125 --
126 -- ----------------------------------------------------------------------------
127 -- |-----------------------------< api_updating >-----------------------------|
128 -- ----------------------------------------------------------------------------
129 -- {Start Of Comments}
130 --
131 -- Description:
132 -- This function is used to populate the g_old_rec record with the
133 -- current row from the database for the specified primary key
134 -- provided that the primary key exists and is valid and does not
135 -- already match the current g_old_rec. The function will always return
136 -- a TRUE value if the g_old_rec is populated with the current row.
137 -- A FALSE value will be returned if all of the primary key arguments
138 -- are null.
139 --
140 -- Prerequisites:
141 -- None.
142 --
143 -- In Parameters:
144 --
145 -- Post Success:
146 -- A value of TRUE will be returned indiciating that the g_old_rec
147 -- is current.
148 -- A value of FALSE will be returned if all of the primary key arguments
149 -- have a null value (this indicates that the row has not be inserted into
150 -- the Schema), and therefore could never have a corresponding row.
151 --
152 -- Post Failure:
153 -- A failure can only occur under two circumstances:
154 -- 1) The primary key is invalid (i.e. a row does not exist for the
155 -- specified primary key values).
156 -- 2) If an object_version_number exists but is NOT the same as the current
157 -- g_old_rec value.
158 --
159 -- Developer Implementation Notes:
160 -- None.
161 --
162 -- Access Status:
163 -- Internal Development Use Only.
164 --
165 -- {End Of Comments}
166 -- ----------------------------------------------------------------------------
167 Function api_updating
168 (p_pending_data_id in number
169 ) Return Boolean;
170 --
171 -- ----------------------------------------------------------------------------
172 -- |---------------------------------< lck >----------------------------------|
173 -- ----------------------------------------------------------------------------
174 -- {Start of comments}
175 --
176 -- Description:
177 -- The Lck process has two main functions to perform. Firstly, the row to be
178 -- updated or deleted must be locked. The locking of the row will only be
179 -- successful if the row is not currently locked by another user.
180 -- Secondly, during the locking of the row, the row is selected into
181 -- the g_old_rec data structure which enables the current row values from
182 -- the server to be available to the api.
183 --
184 -- Prerequisites:
185 -- When attempting to call the lock the object version number (if defined)
186 -- is mandatory.
187 --
188 -- In Parameters:
189 -- The arguments to the Lck process are the primary key(s) which uniquely
190 -- identify the row and the object version number of row.
191 --
192 -- Post Success:
193 -- On successful completion of the Lck process the row to be updated or
194 -- deleted will be locked and selected into the global data structure
195 -- g_old_rec.
196 --
197 -- Post Failure:
198 -- The Lck process can fail for three reasons:
199 -- 1) When attempting to lock the row the row could already be locked by
200 -- another user. This will raise the HR_Api.Object_Locked exception.
201 -- 2) The row which is required to be locked doesn't exist in the HR Schema.
202 -- This error is trapped and reported using the message name
203 -- 'HR_7220_INVALID_PRIMARY_KEY'.
204 -- 3) The row although existing in the HR Schema has a different object
205 -- version number than the object version number specified.
206 -- This error is trapped and reported using the message name
207 -- 'HR_7155_OBJECT_INVALID'.
208 --
209 -- Developer Implementation Notes:
210 -- For each primary key and the object version number arguments add a
211 -- call to hr_api.mandatory_arg_error procedure to ensure that these
212 -- argument values are not null.
213 --
214 -- Access Status:
215 -- Internal Development Use Only.
216 --
217 -- {End of comments}
218 -- ----------------------------------------------------------------------------
219 Procedure lck
220 (p_pending_data_id in number
221 );
222 --
223 -- ----------------------------------------------------------------------------
224 -- |-----------------------------< convert_args >-----------------------------|
225 -- ----------------------------------------------------------------------------
226 -- {Start Of Comments}
227 --
228 -- Description:
229 -- This function is used to turn attribute parameters into the record
230 -- structure parameter g_rec_type.
231 --
232 -- Prerequisites:
233 -- This is a private function and can only be called from the ins or upd
234 -- attribute processes.
235 --
236 -- In Parameters:
237 --
238 -- Post Success:
239 -- A returning record structure will be returned.
240 --
241 -- Post Failure:
242 -- No direct error handling is required within this function. Any possible
243 -- errors within this function will be a PL/SQL value error due to
244 -- conversion of datatypes or data lengths.
245 --
246 -- Developer Implementation Notes:
247 -- None.
248 --
249 -- Access Status:
250 -- Internal Row Handler Use Only.
251 --
252 -- {End Of Comments}
253 -- ----------------------------------------------------------------------------
254 Function convert_args
255 (p_pending_data_id in number
256 ,p_email_address in varchar2
257 ,p_vacancy_id in number
258 ,p_last_name in varchar2
259 ,p_first_name in varchar2
260 ,p_user_password in varchar2
261 ,p_resume_file_name in varchar2
262 ,p_resume_description in varchar2
263 ,p_resume_mime_type in varchar2
264 ,p_source_type in varchar2
265 ,p_job_post_source_name in varchar2
266 ,p_posting_content_id in number
267 ,p_person_id in number
268 ,p_processed in varchar2
269 ,p_sex in varchar2
270 ,p_date_of_birth in date
271 ,p_per_information_category in varchar2
272 ,p_per_information1 in varchar2
273 ,p_per_information2 in varchar2
274 ,p_per_information3 in varchar2
275 ,p_per_information4 in varchar2
276 ,p_per_information5 in varchar2
277 ,p_per_information6 in varchar2
278 ,p_per_information7 in varchar2
279 ,p_per_information8 in varchar2
280 ,p_per_information9 in varchar2
281 ,p_per_information10 in varchar2
282 ,p_per_information11 in varchar2
283 ,p_per_information12 in varchar2
284 ,p_per_information13 in varchar2
285 ,p_per_information14 in varchar2
286 ,p_per_information15 in varchar2
287 ,p_per_information16 in varchar2
288 ,p_per_information17 in varchar2
289 ,p_per_information18 in varchar2
290 ,p_per_information19 in varchar2
291 ,p_per_information20 in varchar2
292 ,p_per_information21 in varchar2
293 ,p_per_information22 in varchar2
294 ,p_per_information23 in varchar2
295 ,p_per_information24 in varchar2
296 ,p_per_information25 in varchar2
297 ,p_per_information26 in varchar2
298 ,p_per_information27 in varchar2
299 ,p_per_information28 in varchar2
300 ,p_per_information29 in varchar2
301 ,p_per_information30 in varchar2
302 ,p_error_message in varchar2
303 ,p_creation_date in date
304 ,p_last_update_date in date
305 ,p_allow_access in varchar2
306 ,p_user_guid in raw
307 ,p_visitor_resp_key in varchar2
308 ,p_visitor_resp_appl_id in number
309 ,p_security_group_key in varchar2
310 )
311 Return g_rec_type;
312 --
313 end irc_ipd_shd;
[Home] [Help]