1 Package per_raa_shd as
2 /* $Header: peraarhi.pkh 120.0 2005/05/31 16:29:25 appldev noship $ */
3 --
4 -- ----------------------------------------------------------------------------
5 -- | Global Record Type Specification |
6 -- ----------------------------------------------------------------------------
7 --
8 Type g_rec_type Is Record
9 (recruitment_activity_id number(15)
10 ,business_group_id number(15)
11 ,authorising_person_id number(10)
12 ,run_by_organization_id number(15)
13 ,internal_contact_person_id number(10)
14 ,parent_recruitment_activity_id number(15)
15 ,currency_code varchar2(15)
16 ,date_start date
17 ,name varchar2(30)
18 ,actual_cost varchar2(30)
19 ,comments varchar2(2000)
20 ,contact_telephone_number varchar2(60)
21 ,date_closing date
22 ,date_end date
23 ,external_contact varchar2(80)
24 ,planned_cost varchar2(30)
25 ,recruiting_site_id number(15)
26 ,recruiting_site_response varchar2(32767)
27 ,last_posted_date date
28 ,type varchar2(30)
29 ,request_id number(15)
30 ,program_application_id number(15)
31 ,program_id number(15)
32 ,program_update_date date
33 ,attribute_category varchar2(30)
34 ,attribute1 varchar2(150)
35 ,attribute2 varchar2(150)
36 ,attribute3 varchar2(150)
37 ,attribute4 varchar2(150)
38 ,attribute5 varchar2(150)
39 ,attribute6 varchar2(150)
40 ,attribute7 varchar2(150)
41 ,attribute8 varchar2(150)
42 ,attribute9 varchar2(150)
43 ,attribute10 varchar2(150)
44 ,attribute11 varchar2(150)
45 ,attribute12 varchar2(150)
46 ,attribute13 varchar2(150)
47 ,attribute14 varchar2(150)
48 ,attribute15 varchar2(150)
49 ,attribute16 varchar2(150)
50 ,attribute17 varchar2(150)
51 ,attribute18 varchar2(150)
52 ,attribute19 varchar2(150)
53 ,attribute20 varchar2(150)
54 ,posting_content_id number(15)
55 ,status varchar2(30)
56 ,object_version_number number(15)
57 );
58 --
59 -- ----------------------------------------------------------------------------
60 -- | Global Definitions - Internal Development Use Only |
61 -- ----------------------------------------------------------------------------
62 --
63 g_old_rec g_rec_type; -- Global record definition
64 g_tab_nam constant varchar2(30) := 'PER_RECRUITMENT_ACTIVITIES';
65 g_recruiting_site_response boolean := false;
66 --
67 -- ----------------------------------------------------------------------------
68 -- |---------------------------< constraint_error >---------------------------|
69 -- ----------------------------------------------------------------------------
70 -- {Start Of Comments}
71 --
72 -- Description:
73 -- This procedure is called when a constraint has been violated (i.e.
74 -- The exception hr_api.check_integrity_violated,
75 -- hr_api.parent_integrity_violated, hr_api.child_integrity_violated or
76 -- hr_api.unique_integrity_violated has been raised).
77 -- The exceptions can only be raised as follows:
78 -- 1) A check constraint can only be violated during an INSERT or UPDATE
79 -- dml operation.
80 -- 2) A parent integrity constraint can only be violated during an
81 -- INSERT or UPDATE dml operation.
82 -- 3) A child integrity constraint can only be violated during an
83 -- DELETE dml operation.
84 -- 4) A unique integrity constraint can only be violated during INSERT or
85 -- UPDATE dml operation.
86 --
87 -- Prerequisites:
88 -- 1) Either hr_api.check_integrity_violated,
89 -- hr_api.parent_integrity_violated, hr_api.child_integrity_violated or
90 -- hr_api.unique_integrity_violated has been raised with the subsequent
91 -- stripping of the constraint name from the generated error message
92 -- text.
93 -- 2) Standalone validation test which corresponds with a constraint error.
94 --
95 -- In Parameter:
96 -- p_constraint_name is in upper format and is just the constraint name
97 -- (e.g. not prefixed by brackets, schema owner etc).
98 --
99 -- Post Success:
100 -- Development dependant.
101 --
102 -- Post Failure:
103 -- Developement dependant.
104 --
105 -- Developer Implementation Notes:
106 -- For each constraint being checked the hr system package failure message
107 -- has been generated as a template only. These system error messages should
108 -- be modified as required (i.e. change the system failure message to a user
109 -- friendly defined error message).
110 --
111 -- Access Status:
112 -- Internal Development Use Only.
113 --
114 -- {End Of Comments}
115 -- ----------------------------------------------------------------------------
116 Procedure constraint_error
117 (p_constraint_name in all_constraints.constraint_name%TYPE);
118 --
119 -- ----------------------------------------------------------------------------
120 -- |-----------------------------< api_updating >-----------------------------|
121 -- ----------------------------------------------------------------------------
122 -- {Start Of Comments}
123 --
124 -- Description:
125 -- This function is used to populate the g_old_rec record with the
126 -- current row from the database for the specified primary key
127 -- provided that the primary key exists and is valid and does not
128 -- already match the current g_old_rec. The function will always return
129 -- a TRUE value if the g_old_rec is populated with the current row.
130 -- A FALSE value will be returned if all of the primary key arguments
131 -- are null.
132 --
133 -- Prerequisites:
134 -- None.
135 --
136 -- In Parameters:
137 --
138 -- Post Success:
139 -- A value of TRUE will be returned indiciating that the g_old_rec
140 -- is current.
141 -- A value of FALSE will be returned if all of the primary key arguments
142 -- have a null value (this indicates that the row has not be inserted into
143 -- the Schema), and therefore could never have a corresponding row.
144 --
145 -- Post Failure:
146 -- A failure can only occur under two circumstances:
147 -- 1) The primary key is invalid (i.e. a row does not exist for the
148 -- specified primary key values).
149 -- 2) If an object_version_number exists but is NOT the same as the current
150 -- g_old_rec value.
151 --
152 -- Developer Implementation Notes:
153 -- None.
154 --
155 -- Access Status:
156 -- Internal Development Use Only.
157 --
158 -- {End Of Comments}
159 -- ----------------------------------------------------------------------------
160 Function api_updating
161 (p_recruitment_activity_id in number
162 ,p_object_version_number in number
163 ) Return Boolean;
164 --
165 -- ----------------------------------------------------------------------------
166 -- |---------------------------------< lck >----------------------------------|
167 -- ----------------------------------------------------------------------------
168 -- {Start of comments}
169 --
170 -- Description:
171 -- The Lck process has two main functions to perform. Firstly, the row to be
172 -- updated or deleted must be locked. The locking of the row will only be
173 -- successful if the row is not currently locked by another user.
174 -- Secondly, during the locking of the row, the row is selected into
175 -- the g_old_rec data structure which enables the current row values from
176 -- the server to be available to the api.
177 --
178 -- Prerequisites:
179 -- When attempting to call the lock the object version number (if defined)
180 -- is mandatory.
181 --
182 -- In Parameters:
183 -- The arguments to the Lck process are the primary key(s) which uniquely
184 -- identify the row and the object version number of row.
185 --
186 -- Post Success:
187 -- On successful completion of the Lck process the row to be updated or
188 -- deleted will be locked and selected into the global data structure
189 -- g_old_rec.
190 --
191 -- Post Failure:
192 -- The Lck process can fail for three reasons:
193 -- 1) When attempting to lock the row the row could already be locked by
194 -- another user. This will raise the HR_Api.Object_Locked exception.
195 -- 2) The row which is required to be locked doesn't exist in the HR Schema.
196 -- This error is trapped and reported using the message name
197 -- 'HR_7220_INVALID_PRIMARY_KEY'.
198 -- 3) The row although existing in the HR Schema has a different object
199 -- version number than the object version number specified.
200 -- This error is trapped and reported using the message name
201 -- 'HR_7155_OBJECT_INVALID'.
202 --
203 -- Developer Implementation Notes:
204 -- For each primary key and the object version number arguments add a
205 -- call to hr_api.mandatory_arg_error procedure to ensure that these
206 -- argument values are not null.
207 --
208 -- Access Status:
209 -- Internal Development Use Only.
210 --
211 -- {End of comments}
212 -- ----------------------------------------------------------------------------
213 Procedure lck
214 (p_recruitment_activity_id in number
215 ,p_object_version_number in number
216 );
217 --
218 -- ----------------------------------------------------------------------------
219 -- |-----------------------------< convert_args >-----------------------------|
220 -- ----------------------------------------------------------------------------
221 -- {Start Of Comments}
222 --
223 -- Description:
224 -- This function is used to turn attribute parameters into the record
225 -- structure parameter g_rec_type.
226 --
227 -- Prerequisites:
228 -- This is a private function and can only be called from the ins or upd
229 -- attribute processes.
230 --
231 -- In Parameters:
232 --
233 -- Post Success:
234 -- A returning record structure will be returned.
235 --
236 -- Post Failure:
237 -- No direct error handling is required within this function. Any possible
238 -- errors within this function will be a PL/SQL value error due to
239 -- conversion of datatypes or data lengths.
240 --
241 -- Developer Implementation Notes:
242 -- None.
243 --
244 -- Access Status:
245 -- Internal Row Handler Use Only.
246 --
247 -- {End Of Comments}
248 -- ----------------------------------------------------------------------------
249 Function convert_args
250 (p_recruitment_activity_id in number
251 ,p_business_group_id in number
252 ,p_authorising_person_id in number
253 ,p_run_by_organization_id in number
254 ,p_internal_contact_person_id in number
255 ,p_parent_recruitment_activity in number
256 ,p_currency_code in varchar2
257 ,p_date_start in date
258 ,p_name in varchar2
259 ,p_actual_cost in varchar2
260 ,p_comments in varchar2
261 ,p_contact_telephone_number in varchar2
262 ,p_date_closing in date
263 ,p_date_end in date
264 ,p_external_contact in varchar2
265 ,p_planned_cost in varchar2
266 ,p_recruiting_site_id in number
267 ,p_recruiting_site_response in varchar2
268 ,p_last_posted_date in date
269 ,p_type in varchar2
270 ,p_request_id in number
271 ,p_program_application_id in number
272 ,p_program_id in number
273 ,p_program_update_date in date
274 ,p_attribute_category in varchar2
275 ,p_attribute1 in varchar2
276 ,p_attribute2 in varchar2
277 ,p_attribute3 in varchar2
278 ,p_attribute4 in varchar2
279 ,p_attribute5 in varchar2
280 ,p_attribute6 in varchar2
281 ,p_attribute7 in varchar2
282 ,p_attribute8 in varchar2
283 ,p_attribute9 in varchar2
284 ,p_attribute10 in varchar2
285 ,p_attribute11 in varchar2
286 ,p_attribute12 in varchar2
287 ,p_attribute13 in varchar2
288 ,p_attribute14 in varchar2
289 ,p_attribute15 in varchar2
290 ,p_attribute16 in varchar2
291 ,p_attribute17 in varchar2
292 ,p_attribute18 in varchar2
293 ,p_attribute19 in varchar2
294 ,p_attribute20 in varchar2
295 ,p_posting_content_id in number
296 ,p_status in varchar2
297 ,p_object_version_number in number
298 )
299 Return g_rec_type;
300 --
301 end per_raa_shd;
[Home] [Help]