1 Package hr_per_type_usage_internal AUTHID CURRENT_USER as
2 /* $Header: peptubsi.pkh 120.0.12010000.2 2008/09/12 11:07:56 ghshanka ship $ */
3 --
4 -- ----------------------------------------------------------------------------
5 -- |------------------------< create_person_type_usage >------------------------|
6 -- ----------------------------------------------------------------------------
7 -- {Start Of Comments}
8 --
9 -- Description:
10 --
11 -- Prerequisites:
12 --
13 --
14 -- In Parameters:
15 -- Name Reqd Type Description
16 -- p_validate Yes boolean If true, the database remains
17 -- unchanged, otherwise the row
18 -- is created on the database.
19 -- p_person_id Yes number Person's Id
20 -- p_person_type_id Yes number Person Type for person
21 -- p_attribute_category No varchar2 Descriptive Flexfield
22 -- p_attribute1 No varchar2 Descriptive Flexfield
23 -- p_attribute2 No varchar2 Descriptive Flexfield
24 -- p_attribute3 No varchar2 Descriptive Flexfield
28 -- p_attribute7 No varchar2 Descriptive Flexfield
25 -- p_attribute4 No varchar2 Descriptive Flexfield
26 -- p_attribute5 No varchar2 Descriptive Flexfield
27 -- p_attribute6 No varchar2 Descriptive Flexfield
29 -- p_attribute8 No varchar2 Descriptive Flexfield
30 -- p_attribute9 No varchar2 Descriptive Flexfield
31 -- p_attribute10 No varchar2 Descriptive Flexfield
32 -- p_attribute11 No varchar2 Descriptive Flexfield
33 -- p_attribute12 No varchar2 Descriptive Flexfield
34 -- p_attribute13 No varchar2 Descriptive Flexfield
35 -- p_attribute14 No varchar2 Descriptive Flexfield
36 -- p_attribute15 No varchar2 Descriptive Flexfield
37 -- p_attribute16 No varchar2 Descriptive Flexfield
38 -- p_attribute17 No varchar2 Descriptive Flexfield
39 -- p_attribute18 No varchar2 Descriptive Flexfield
40 -- p_attribute19 No varchar2 Descriptive Flexfield
41 -- p_attribute20 No varchar2 Descriptive Flexfield
42 -- p_attribute21 No varchar2 Descriptive Flexfield
43 -- p_attribute22 No varchar2 Descriptive Flexfield
44 -- p_attribute23 No varchar2 Descriptive Flexfield
45 -- p_attribute24 No varchar2 Descriptive Flexfield
46 -- p_attribute25 No varchar2 Descriptive Flexfield
47 -- p_attribute26 No varchar2 Descriptive Flexfield
48 -- p_attribute27 No varchar2 Descriptive Flexfield
49 -- p_attribute28 No varchar2 Descriptive Flexfield
50 -- p_attribute29 No varchar2 Descriptive Flexfield
51 -- p_attribute30 No varchar2 Descriptive Flexfield
52 -- p_effective_date Yes date Session Date.
53 --
54 -- Post Success:
55 -- When the person type usage has been successfully inserted, the following
56 -- OUT parms are set.
57 --
58 -- Out Parameters:
59 -- Name Reqd Type Description
60 -- p_person_type_usage_id Yes number If p_validate is set to false, then
61 -- this uniquely identifies the new
62 -- record, else it contains null.
63 -- p_effective_start_date Yes date If p_validate is set to false, then
64 -- this will be set to the effective
65 -- start date of the record, else it
66 -- will be set to null.
67 -- p_effective_end_date Yes date If p_validate is set to false, then
68 -- this will be set to the effective
69 -- end date of the record, else it
70 -- will be set to null.
71 -- p_object_version_number Yes number If p_validate is set to false, then
72 -- this will be set to the version
73 -- number of the record, else it
74 -- will be set to null.
75 --
76 -- Post Failure:
77 -- The API does not create the person type usage and raises an error.
78 --
79 -- Access Status:
80 -- Internal.
81 --
82 -- {End Of Comments}
83 --
84 procedure create_person_type_usage
85 (
86 p_validate in boolean default false
87 ,p_person_id in number
88 ,p_person_type_id in number
89 ,p_effective_date in date
90 ,p_attribute_category in varchar2 default null
91 ,p_attribute1 in varchar2 default null
92 ,p_attribute2 in varchar2 default null
93 ,p_attribute3 in varchar2 default null
94 ,p_attribute4 in varchar2 default null
95 ,p_attribute5 in varchar2 default null
96 ,p_attribute6 in varchar2 default null
97 ,p_attribute7 in varchar2 default null
98 ,p_attribute8 in varchar2 default null
99 ,p_attribute9 in varchar2 default null
100 ,p_attribute10 in varchar2 default null
101 ,p_attribute11 in varchar2 default null
102 ,p_attribute12 in varchar2 default null
103 ,p_attribute13 in varchar2 default null
104 ,p_attribute14 in varchar2 default null
105 ,p_attribute15 in varchar2 default null
106 ,p_attribute16 in varchar2 default null
107 ,p_attribute17 in varchar2 default null
108 ,p_attribute18 in varchar2 default null
109 ,p_attribute19 in varchar2 default null
110 ,p_attribute20 in varchar2 default null
111 ,p_attribute21 in varchar2 default null
112 ,p_attribute22 in varchar2 default null
113 ,p_attribute23 in varchar2 default null
114 ,p_attribute24 in varchar2 default null
115 ,p_attribute25 in varchar2 default null
116 ,p_attribute26 in varchar2 default null
117 ,p_attribute27 in varchar2 default null
121 ,p_person_type_usage_id out nocopy number
118 ,p_attribute28 in varchar2 default null
119 ,p_attribute29 in varchar2 default null
120 ,p_attribute30 in varchar2 default null
122 ,p_object_version_number out nocopy number
123 ,p_effective_start_date out nocopy date
124 ,p_effective_end_date out nocopy date
125 );
126 --
127 -- ----------------------------------------------------------------------------
128 -- |------------------------< delete_person_type_usage >------------------------|
129 -- ----------------------------------------------------------------------------
130 -- {Start Of Comments}
131 --
132 -- Description:
133 --
134 -- Prerequisites:
135 --
136 --
137 -- In Parameters:
138 -- Name Reqd Type Description
139 -- p_validate Yes boolean If true, the database remains
140 -- unchanged, otherwise the row
141 -- is created on the database.
142 -- p_person_type_usage_id Yes number ID of person usage type to
143 -- be deleted.
144 -- p_effective_date Yes date Date on which record is to
145 -- be deleted.
146 -- p_datetrack_mode Yes varchar2 Datetrack mode of delete.
147 -- Currently only DELETE and
148 -- ZAP are supported.
149 --
150 -- Post Success:
151 -- When the person type usage has been successfully deleted, the following
152 -- OUT parms are set. All of the below parameters will be set to NULL if the
153 -- datetrack delete mode is set to ZAP.
154 --
155 -- Name Reqd Type Description
156 -- p_effective_start_date Yes date If p_validate is set to false, then
157 -- this will be set to the effective
158 -- start date of the record, else it
159 -- will be set to null.
160 -- p_effective_end_date Yes date If p_validate is set to false, then
161 -- this will be set to the effective
162 -- end date of the record, else it
163 -- will be set to null.
164 -- p_object_version_number Yes number If p_validate is set to false, then
165 -- this will be set to the version
166 -- number of the record, else it
167 -- will be set to null.
168 -- Post Failure:
169 -- The API does not delete the person type usage and raises an error.
170 --
171 -- Access Status:
172 -- Internal.
173 --
174 -- {End Of Comments}
175 --
176 procedure delete_person_type_usage
177 (
178 p_validate in boolean default false
179 ,p_person_type_usage_id in number
180 ,p_effective_date in date
181 ,p_datetrack_mode in varchar2
182 ,p_object_version_number in out nocopy number
183 ,p_effective_start_date out nocopy date
184 ,p_effective_end_date out nocopy date
185 );
186 --
187 -- ----------------------------------------------------------------------------
188 -- |------------------------< update_person_type_usage >------------------------|
189 -- ----------------------------------------------------------------------------
190 -- {Start Of Comments}
191 --
192 -- Description:
193 --
194 -- Prerequisites:
195 --
196 --
197 -- In Parameters:
201 -- is updated on the database.
198 -- Name Reqd Type Description
199 -- p_validate Yes boolean If true, the database remains
200 -- unchanged, otherwise the row
202 -- p_effective_date Yes date Session Date.
203 -- p_datetrack_mode Yes varchar2 Datetrack update mode
204 -- p_person_type_usage_id Yes number Person Type Usage Identifier
205 -- p_object_version_number Yes number Object version number for
206 -- Person type usage
207 -- p_person_type_id No number Person type identifier
208 -- p_attribute_category No varchar2 Descriptive Flexfield
209 -- p_attribute1 No varchar2 Descriptive Flexfield
210 -- p_attribute2 No varchar2 Descriptive Flexfield
211 -- p_attribute3 No varchar2 Descriptive Flexfield
212 -- p_attribute4 No varchar2 Descriptive Flexfield
213 -- p_attribute5 No varchar2 Descriptive Flexfield
214 -- p_attribute6 No varchar2 Descriptive Flexfield
215 -- p_attribute7 No varchar2 Descriptive Flexfield
216 -- p_attribute8 No varchar2 Descriptive Flexfield
217 -- p_attribute9 No varchar2 Descriptive Flexfield
218 -- p_attribute10 No varchar2 Descriptive Flexfield
219 -- p_attribute11 No varchar2 Descriptive Flexfield
220 -- p_attribute12 No varchar2 Descriptive Flexfield
221 -- p_attribute13 No varchar2 Descriptive Flexfield
222 -- p_attribute14 No varchar2 Descriptive Flexfield
223 -- p_attribute15 No varchar2 Descriptive Flexfield
224 -- p_attribute16 No varchar2 Descriptive Flexfield
225 -- p_attribute17 No varchar2 Descriptive Flexfield
226 -- p_attribute18 No varchar2 Descriptive Flexfield
227 -- p_attribute19 No varchar2 Descriptive Flexfield
228 -- p_attribute20 No varchar2 Descriptive Flexfield
229 -- p_attribute21 No varchar2 Descriptive Flexfield
230 -- p_attribute22 No varchar2 Descriptive Flexfield
231 -- p_attribute23 No varchar2 Descriptive Flexfield
232 -- p_attribute24 No varchar2 Descriptive Flexfield
233 -- p_attribute25 No varchar2 Descriptive Flexfield
234 -- p_attribute26 No varchar2 Descriptive Flexfield
235 -- p_attribute27 No varchar2 Descriptive Flexfield
236 -- p_attribute28 No varchar2 Descriptive Flexfield
237 -- p_attribute29 No varchar2 Descriptive Flexfield
241 -- When the person type usage has been successfully updated, the following
238 -- p_attribute30 No varchar2 Descriptive Flexfield
239 --
240 -- Post Success:
242 -- OUT parms are set.
243 --
244 -- Out Parameters:
245 -- Name Reqd Type Description
246 -- p_object_version_number Yes number If p_validate is set to false, then
247 -- this will be set to the version
248 -- number of the record, else it
249 -- will be set to null.
250 -- p_effective_start_date Yes date If p_validate is set to false, then
251 -- this will be set to the effective
252 -- start date of the record, else it
253 -- will be set to null.
254 -- p_effective_end_date Yes date If p_validate is set to false, then
255 -- this will be set to the effective
256 -- end date of the record, else it
257 -- will be set to null.
258 --
259 -- Post Failure:
260 -- The API does not update the person type usage and raises an error.
261 --
262 -- Access Status:
263 -- Internal.
264 --
265 -- {End Of Comments}
266 --
267 procedure update_person_type_usage
268 (
269 p_validate in boolean default false
270 ,p_effective_date in date
271 ,p_datetrack_mode in varchar2
272 ,p_person_type_usage_id in number
273 ,p_object_version_number in out nocopy number
274 ,p_person_type_id in number default hr_api.g_number
275 ,p_attribute_category in varchar2 default hr_api.g_varchar2
276 ,p_attribute1 in varchar2 default hr_api.g_varchar2
277 ,p_attribute2 in varchar2 default hr_api.g_varchar2
278 ,p_attribute3 in varchar2 default hr_api.g_varchar2
279 ,p_attribute4 in varchar2 default hr_api.g_varchar2
280 ,p_attribute5 in varchar2 default hr_api.g_varchar2
281 ,p_attribute6 in varchar2 default hr_api.g_varchar2
282 ,p_attribute7 in varchar2 default hr_api.g_varchar2
283 ,p_attribute8 in varchar2 default hr_api.g_varchar2
284 ,p_attribute9 in varchar2 default hr_api.g_varchar2
285 ,p_attribute10 in varchar2 default hr_api.g_varchar2
286 ,p_attribute11 in varchar2 default hr_api.g_varchar2
287 ,p_attribute12 in varchar2 default hr_api.g_varchar2
288 ,p_attribute13 in varchar2 default hr_api.g_varchar2
289 ,p_attribute14 in varchar2 default hr_api.g_varchar2
290 ,p_attribute15 in varchar2 default hr_api.g_varchar2
291 ,p_attribute16 in varchar2 default hr_api.g_varchar2
292 ,p_attribute17 in varchar2 default hr_api.g_varchar2
293 ,p_attribute18 in varchar2 default hr_api.g_varchar2
294 ,p_attribute19 in varchar2 default hr_api.g_varchar2
295 ,p_attribute20 in varchar2 default hr_api.g_varchar2
296 ,p_attribute21 in varchar2 default hr_api.g_varchar2
297 ,p_attribute22 in varchar2 default hr_api.g_varchar2
298 ,p_attribute23 in varchar2 default hr_api.g_varchar2
299 ,p_attribute24 in varchar2 default hr_api.g_varchar2
300 ,p_attribute25 in varchar2 default hr_api.g_varchar2
301 ,p_attribute26 in varchar2 default hr_api.g_varchar2
302 ,p_attribute27 in varchar2 default hr_api.g_varchar2
303 ,p_attribute28 in varchar2 default hr_api.g_varchar2
304 ,p_attribute29 in varchar2 default hr_api.g_varchar2
305 ,p_attribute30 in varchar2 default hr_api.g_varchar2
306 ,p_effective_start_date out nocopy date
307 ,p_effective_end_date out nocopy date
308 );
309 --
310 -- ----------------------------------------------------------------------------
311 -- |----------------------< maintain_person_type_usage >----------------------|
312 -- ----------------------------------------------------------------------------
313 --
314 -- {Start Of Comments}
315 --
316 -- Description:
317 --
318 -- Prerequisites:
319 --
320 --
321 -- In Parameters:
322 -- Name Reqd Type Description
323 -- p_effective_date Yes date Session Date.
324 -- p_person_id Yes number Person identifier
325 -- p_person_type_id Yes number Person type identifier
326 -- p_datetrack_update_mode No varchar2 Datetrack update mode
327 -- p_datetrack_delete_mode No varchar2 Datetrack delete mode
328 --
329 -- Post Success:
330 -- When the person type usage has been successfully maintained, the following
331 -- OUT parms are set.
332 --
333 -- Post Failure:
334 -- The API does not update the person type usage and raises an error.
335 --
336 -- Access Status:
337 -- Internal.
338 --
339 -- {End Of Comments}
340 --
341 procedure maintain_person_type_usage
342 (
346 ,p_datetrack_update_mode in varchar2 default hr_api.g_update
343 p_effective_date in date
344 ,p_person_id in number
345 ,p_person_type_id in number
347 ,p_datetrack_delete_mode in varchar2 default null
348 );
349 --
350 -- ----------------------------------------------------------------------------
351 -- |-----------------------< cancel_person_type_usage >-----------------------|
352 -- ----------------------------------------------------------------------------
353 --
354 -- {Start Of Comments}
355 --
356 -- Description:
357 --
358 -- Prerequisites:
359 --
360 --
361 -- In Parameters:
362 -- Name Reqd Type Description
363 -- p_effective_date Yes date Session Date.
364 -- p_person_id Yes number Person identifier
365 -- p_system_person_type Yes varchar2 System person type
366 --
367 -- Post Success:
368 -- When the person type usage has been successfully cancelled, the following
369 -- OUT parms are set.
370 --
371 -- Post Failure:
372 -- The API does not cancel the person type usage and raises an error.
373 --
374 -- Access Status:
375 -- Internal.
376 --
377 -- {End Of Comments}
378 --
379 procedure cancel_person_type_usage
380 (
381 p_effective_date in date
382 ,p_person_id in number
383 ,p_system_person_type in varchar2
384 );
385 --
386
387 -- ----------------------------------------------------------------------------
388 -- |-----------------------< cancel_emp_apl_ptu >-----------------------|
389 -- ----------------------------------------------------------------------------
390 --
391 -- {Start Of Comments}
392 --
393 -- Description:
394 --
395 -- Prerequisites:
396 --
397 --
398 -- In Parameters:
399 -- Name Reqd Type Description
400 -- p_effective_date Yes date Session Date.
401 -- p_person_id Yes number Person identifier
402 -- p_system_person_type Yes varchar2 System person type
403 --
404 -- Post Success:
405 -- When the person type usage has been successfully cancelled, the following
406 -- OUT parms are set.
407 --
408 -- Post Failure:
409 -- The API does not cancel the person type usage and raises an error.
410 --
411 -- Access Status:
412 -- Internal.
413 --
414 -- {End Of Comments}
415 --
416 procedure cancel_emp_apl_ptu
417 (
418 p_effective_date in date
419 ,p_person_id in number
420 ,p_system_person_type in varchar2
421 );
422 --
423 -- ----------------------------------------------------------------------------
424 -- |------------------------< change_hire_date_ptu >---------------------------|
425 -- ----------------------------------------------------------------------------
426 --
427 -- {Start Of Comments}
428 --
429 -- Description:
430 --
431 -- Prerequisites:
432 --
433 --
434 -- In Parameters:
435 -- Name Reqd Type Description
436 -- p_date_start Yes date new hire date
437 -- p_old_date_start Yes date old hire date
438 -- p_person_id Yes number Person identifier
439 -- p_system_person_type Yes varchar2 System person type
440 --
441 -- Post Success:
442 -- When the hire date has been changed and the PTU record updated accordingly
443 -- the following OUT parms are set.
444 --
445 -- Post Failure:
446 -- The API does not move the start date of the PTU record and raise an error.
447 --
448 -- Access Status:
449 -- Internal.
450 --
451 -- {End Of Comments}
452 --
453 procedure change_hire_date_ptu
454 (
455 p_date_start in date
456 ,p_old_date_start in date
457 ,p_person_id in number
458 ,p_system_person_type in varchar2
459 );
460 --
461 end hr_per_type_usage_internal;
[Home] [Help]