1 Package hr_mass_move_cus AUTHID CURRENT_USER as
2 /* $Header: pemmvcus.pkh 115.1 99/07/18 14:02:49 porting ship $ */
3 --
4 -- ----------------------------------------------------------------------------
5 -- |------------------------< pre_move_emp_asg >---------------------------|
6 -- ----------------------------------------------------------------------------
7 -- {Start Of Comments}
8 --
9 -- Description:
10 -- The pre-core move employee assignment procedure is delivered as an 'empty'
11 -- packaged procedure which the customer can customize by coding any additional
12 -- validation which they may require at assignment level before an employee
13 -- assignment is moved.
14 --
15 --
16 -- Prerequisites:
17 --
18 --
19 -- In Parameters:
20 -- Name Reqd Type Description
21 -- p_effective_date Yes date Date the assignment is being moved
22 -- p_assignment_id Yes number The Assignment that is being moved
23 -- p_object_version_number Yes number The object version number of the
24 -- assignment which is to be moved.
25 -- p_mass_move_id No number If the Assignment is being moved as
26 -- part of a mass move, this is the
27 -- particular mass move by which it is
28 -- being moved.
29 -- p_position_id No number Position to which the assignment is
30 -- being moved.
31 -- p_organization_id No number Organization to which the
32 -- assignment is being moved.
33 -- p_location_id No number Location to which the assignment is
34 -- being moved.
35 -- p_frequency No varchar2 New Frequency of Normal Working
36 -- Hours for the Asg.
37 -- p_normal_hours No number New Normal Working Hours for the asg
38 -- p_time_normal_finish No varchar2 New Normal finish time for the asg.
39 -- p_time_normal_start No varchar2 New Normal start time for the asg.
40 -- p_segment1 No varchar2 Soft Coding Keyflex.
41 -- p_segment2 No varchar2 Soft Coding Keyflex.
42 -- p_segment3 No varchar2 Soft Coding Keyflex.
43 -- p_segment4 No varchar2 Soft Coding Keyflex.
44 -- p_segment5 No varchar2 Soft Coding Keyflex.
45 -- p_segment6 No varchar2 Soft Coding Keyflex.
46 -- p_segment7 No varchar2 Soft Coding Keyflex.
47 -- p_segment8 No varchar2 Soft Coding Keyflex.
48 -- p_segment9 No varchar2 Soft Coding Keyflex.
49 -- p_segment10 No varchar2 Soft Coding Keyflex.
50 -- p_segment11 No varchar2 Soft Coding Keyflex.
51 -- p_segment12 No varchar2 Soft Coding Keyflex.
52 -- p_segment13 No varchar2 Soft Coding Keyflex.
53 -- p_segment14 No varchar2 Soft Coding Keyflex.
54 -- p_segment15 No varchar2 Soft Coding Keyflex.
55 -- p_segment16 No varchar2 Soft Coding Keyflex.
56 -- p_segment17 No varchar2 Soft Coding Keyflex.
57 -- p_segment18 No varchar2 Soft Coding Keyflex.
58 -- p_segment19 No varchar2 Soft Coding Keyflex.
59 -- p_segment20 No varchar2 Soft Coding Keyflex.
60 -- p_segment21 No varchar2 Soft Coding Keyflex.
61 -- p_segment22 No varchar2 Soft Coding Keyflex.
62 -- p_segment23 No varchar2 Soft Coding Keyflex.
63 -- p_segment24 No varchar2 Soft Coding Keyflex.
64 -- p_segment25 No varchar2 Soft Coding Keyflex.
65 -- p_segment26 No varchar2 Soft Coding Keyflex.
66 -- p_segment27 No varchar2 Soft Coding Keyflex.
67 -- p_segment28 No varchar2 Soft Coding Keyflex.
68 -- p_segment29 No varchar2 Soft Coding Keyflex.
69 -- p_segment30 No varchar2 Soft Coding Keyflex.
70 --
71 -- Post Success:
72 -- The pre-move assignemnt validation has been successful, ie. the assignment
73 -- has been validated for moving, and processing by the core move_emp_asg
74 -- proceeds.
75 --
76 -- Post Failure:
77 -- The assignment has not been successful validated for moving and an
78 -- error is raised.
79 --
80 -- Access Status:
81 -- Public.
82 --
83 -- {End Of Comments}
84 --
85 procedure pre_move_emp_asg
86 (p_effective_date in date
87 ,p_assignment_id in number
88 ,p_object_version_number in number
89 ,p_mass_move_id in number default hr_api.g_number
93 ,p_frequency in varchar2 default hr_api.g_varchar2
90 ,p_position_id in number default hr_api.g_number
91 ,p_organization_id in number default hr_api.g_number
92 ,p_location_id in number default hr_api.g_number
94 ,p_normal_hours in number default hr_api.g_number
95 ,p_time_normal_finish in varchar2 default hr_api.g_varchar2
96 ,p_time_normal_start in varchar2 default hr_api.g_varchar2
97 ,p_segment1 in varchar2 default hr_api.g_varchar2
98 ,p_segment2 in varchar2 default hr_api.g_varchar2
99 ,p_segment3 in varchar2 default hr_api.g_varchar2
100 ,p_segment4 in varchar2 default hr_api.g_varchar2
101 ,p_segment5 in varchar2 default hr_api.g_varchar2
102 ,p_segment6 in varchar2 default hr_api.g_varchar2
103 ,p_segment7 in varchar2 default hr_api.g_varchar2
104 ,p_segment8 in varchar2 default hr_api.g_varchar2
105 ,p_segment9 in varchar2 default hr_api.g_varchar2
106 ,p_segment10 in varchar2 default hr_api.g_varchar2
107 ,p_segment11 in varchar2 default hr_api.g_varchar2
108 ,p_segment12 in varchar2 default hr_api.g_varchar2
109 ,p_segment13 in varchar2 default hr_api.g_varchar2
110 ,p_segment14 in varchar2 default hr_api.g_varchar2
111 ,p_segment15 in varchar2 default hr_api.g_varchar2
112 ,p_segment16 in varchar2 default hr_api.g_varchar2
113 ,p_segment17 in varchar2 default hr_api.g_varchar2
114 ,p_segment18 in varchar2 default hr_api.g_varchar2
115 ,p_segment19 in varchar2 default hr_api.g_varchar2
116 ,p_segment20 in varchar2 default hr_api.g_varchar2
117 ,p_segment21 in varchar2 default hr_api.g_varchar2
118 ,p_segment22 in varchar2 default hr_api.g_varchar2
119 ,p_segment23 in varchar2 default hr_api.g_varchar2
120 ,p_segment24 in varchar2 default hr_api.g_varchar2
121 ,p_segment25 in varchar2 default hr_api.g_varchar2
122 ,p_segment26 in varchar2 default hr_api.g_varchar2
123 ,p_segment27 in varchar2 default hr_api.g_varchar2
124 ,p_segment28 in varchar2 default hr_api.g_varchar2
125 ,p_segment29 in varchar2 default hr_api.g_varchar2
126 ,p_segment30 in varchar2 default hr_api.g_varchar2
127 );
128 --
129 -- ----------------------------------------------------------------------------
130 -- |------------------------< post_move_emp_asg >---------------------------|
131 -- ----------------------------------------------------------------------------
132 --
133 -- {Start Of Comments}
134 --
135 -- Description:
136 -- The post-core move employee assignment procedure is delivered as an 'empty'
137 -- packaged procedure which the customer can customize by coding any additional
138 -- DML which they may require at assignment level before an employee
139 -- assignment is moved.
140 --
141 -- Prerequisites:
142 --
143 --
144 -- In Parameters:
145 -- Name Reqd Type Description
146 -- p_validate Yes boolean If true, the database
147 -- remains unchanged. If false,
148 -- the assignment is updated.
149 -- p_old_asg_eff_start_date Yes date This is the effective start date
150 -- of the 'old' assignment row, ie.
151 -- the latest row which existed
152 -- for the assignment prior to
153 -- the move and whose effective end
154 -- date is now the day before the
155 -- move date.
156 -- p_new_asg_eff_start_date Yes date This is the effective start date
157 -- of the 'new' assignment row, ie.
158 -- the row whose effective start
159 -- date is equal to the move date.
160 -- p_assignment_id Yes number The assignment which was moved.
161 -- p_old_asg_object_version_num Yes number The object version number of
162 -- the 'old' assignment row.
163 -- p_new_asg_object_version_num Yes number The object version number of
164 -- the 'new' assignment row.
165 --
166 -- Post Success:
167 -- When the post-move assignment DML is successful, the following out
168 -- parameters are set :
169 -- Name Type Description
170 -- p_old_asg_object_version_num number
171 -- p_new_asg_object_version_num number
172 --
173 --
174 -- Post Failure:
175 -- The API does not update the Assignment and raises an error.
176 --
177 -- Access Status:
178 -- Public.
179 --
180 -- {End Of Comments}
181 --
182 --
183 procedure post_move_emp_asg
184 (p_validate in boolean default false
185 ,p_old_asg_eff_start_date in out date
186 ,p_new_asg_eff_start_date in out date
187 ,p_assignment_id in number
188 ,p_old_asg_object_version_num in out number
189 ,p_new_asg_object_version_num in out number
190 ,p_mass_move_id in number default hr_api.g_number
191 );
192 --
193 -- ----------------------------------------------------------------------------
194 -- |------------------------< pre_move_position >---------------------------|
195 -- ----------------------------------------------------------------------------
196 -- {Start Of Comments}
197 --
198 -- Description:
202 -- moved.
199 -- The pre-core move position procedure is delivered as an 'empty'
200 -- packaged procedure which the customer can customize by coding any additional
201 -- validation which they may require at position level before position is
203 --
204 --
205 -- Prerequisites:
206 --
207 --
208 -- In Parameters:
209 -- Name Reqd Type Description
210 -- p_position_id Yes number The position which is to be moved.
211 -- p_object_version_number Yes number The object version number of the
212 -- position which is to be moved.
213 -- p_date_effective Yes date The start date of the new position
214 -- position which is to be created.
215 -- p_organization_id Yes number The Organization to which the
216 -- position is to be moved, ie. the
217 -- Organization for which the new
218 -- position is to be created.
219 -- p_segment1 No varchar2 Key flex for position definition.
220 -- p_segment2 No varchar2 Key flex for position definition.
221 -- p_segment3 No varchar2 Key flex for position definition.
222 -- p_segment4 No varchar2 Key flex for position definition.
223 -- p_segment5 No varchar2 Key flex for position definition.
224 -- p_segment6 No varchar2 Key flex for position definition.
225 -- p_segment7 No varchar2 Key flex for position definition.
226 -- p_segment8 No varchar2 Key flex for position definition.
227 -- p_segment9 No varchar2 Key flex for position definition.
228 -- p_segment10 No varchar2 Key flex for position definition.
229 -- p_segment11 No varchar2 Key flex for position definition.
230 -- p_segment12 No varchar2 Key flex for position definition.
231 -- p_segment13 No varchar2 Key flex for position definition.
232 -- p_segment14 No varchar2 Key flex for position definition.
233 -- p_segment15 No varchar2 Key flex for position definition.
234 -- p_segment16 No varchar2 Key flex for position definition.
235 -- p_segment17 No varchar2 Key flex for position definition.
236 -- p_segment18 No varchar2 Key flex for position definition.
237 -- p_segment19 No varchar2 Key flex for position definition.
238 -- p_segment20 No varchar2 Key flex for position definition.
239 -- p_segment21 No varchar2 Key flex for position definition.
240 -- p_segment22 No varchar2 Key flex for position definition.
241 -- p_segment23 No varchar2 Key flex for position definition.
242 -- p_segment24 No varchar2 Key flex for position definition.
243 -- p_segment25 No varchar2 Key flex for position definition.
244 -- p_segment26 No varchar2 Key flex for position definition.
245 -- p_segment27 No varchar2 Key flex for position definition.
246 -- p_segment28 No varchar2 Key flex for position definition.
247 -- p_segment29 No varchar2 Key flex for position definition.
248 -- p_segment30 No varchar2 Key flex for position definition.
249 -- p_deactivate_old_position No boolean When this is set to TRUE the 'old'
250 -- position, ie. P_POSITION_ID is
251 -- closed down, ie. its end date is set
252 -- to the day before P_DATE_EFFECTIVE.
253 -- When this argument is set to FALSE,
254 -- the old position is not closed down.
255 -- p_mass_move_id No number Where this Business Process is being
256 -- called as part of Mass Move, this is
257 -- the particular mass move that is
258 -- being processed.
259 --
260 -- Post Success:
261 -- The pre-move position validation has been successful, ie. the position
262 -- has been validated for moving, and processing by the core move_position
263 -- proceeds.
264 --
265 -- Post Failure:
266 -- The position has not been successfully validated for moving and an
267 -- error is raised.
268 --
269 -- Access Status:
270 -- Public.
271 --
272 -- {End Of Comments}
273 --
274 procedure pre_move_position
275 (p_position_id in number
276 ,p_object_version_number in number
277 ,p_date_effective in date
278 ,p_business_group_id in number
279 ,p_organization_id in number
280 ,p_segment1 in varchar2 default hr_api.g_varchar2
281 ,p_segment2 in varchar2 default hr_api.g_varchar2
282 ,p_segment3 in varchar2 default hr_api.g_varchar2
283 ,p_segment4 in varchar2 default hr_api.g_varchar2
284 ,p_segment5 in varchar2 default hr_api.g_varchar2
285 ,p_segment6 in varchar2 default hr_api.g_varchar2
286 ,p_segment7 in varchar2 default hr_api.g_varchar2
287 ,p_segment8 in varchar2 default hr_api.g_varchar2
288 ,p_segment9 in varchar2 default hr_api.g_varchar2
289 ,p_segment10 in varchar2 default hr_api.g_varchar2
290 ,p_segment11 in varchar2 default hr_api.g_varchar2
291 ,p_segment12 in varchar2 default hr_api.g_varchar2
292 ,p_segment13 in varchar2 default hr_api.g_varchar2
293 ,p_segment14 in varchar2 default hr_api.g_varchar2
294 ,p_segment15 in varchar2 default hr_api.g_varchar2
295 ,p_segment16 in varchar2 default hr_api.g_varchar2
296 ,p_segment17 in varchar2 default hr_api.g_varchar2
297 ,p_segment18 in varchar2 default hr_api.g_varchar2
301 ,p_segment22 in varchar2 default hr_api.g_varchar2
298 ,p_segment19 in varchar2 default hr_api.g_varchar2
299 ,p_segment20 in varchar2 default hr_api.g_varchar2
300 ,p_segment21 in varchar2 default hr_api.g_varchar2
302 ,p_segment23 in varchar2 default hr_api.g_varchar2
303 ,p_segment24 in varchar2 default hr_api.g_varchar2
304 ,p_segment25 in varchar2 default hr_api.g_varchar2
305 ,p_segment26 in varchar2 default hr_api.g_varchar2
306 ,p_segment27 in varchar2 default hr_api.g_varchar2
307 ,p_segment28 in varchar2 default hr_api.g_varchar2
308 ,p_segment29 in varchar2 default hr_api.g_varchar2
309 ,p_segment30 in varchar2 default hr_api.g_varchar2
310 ,p_deactivate_old_position in boolean default false
311 ,p_mass_move_id in number default hr_api.g_number
312 );
313 --
314 -- ----------------------------------------------------------------------------
315 -- |------------------------< post_move_position >---------------------------|
316 -- ----------------------------------------------------------------------------
317 --
318 -- {Start Of Comments}
319 --
320 -- Description:
321 -- The post-core move position procedure is delivered as an 'empty' packaged
322 -- procedure which the customer can customize by coding any additional
323 -- DML which they may require at position level before a position is moved.
324 --
325 -- Prerequisites:
326 --
327 --
328 -- In Parameters:
329 -- Name Reqd Type Description
330 -- p_validate No boolean If true, the database
331 -- remains unchanged. If false,
332 -- the assignment is updated.
333 -- p_position_id Yes number The 'old' position which was
334 -- moved.
335 -- p_object_version_number Yes number The object version number of
336 -- the 'old' position, ie. the
337 -- position which was moved.
338 -- p_date_effective Yes date The start date of the new
339 -- position which is to be created.
340 -- p_business_group_id Yes number The business group of the old
341 -- and new positions.
342 -- p_organization_id Yes number The organization to which the
343 -- position was moved.
344 -- p_deactivate_old_position No boolean When this is set to TRUE the
345 -- 'old' position, ie.
346 -- P_POSITION_ID was closed down,
347 -- ie. its end date was set to the
348 -- day before P_DATE_EFFECTIVE.
349 -- When this argument is set to
350 -- FALSE, the old position was not
351 -- closed down.
352 -- p_new_position_id Yes number The new position which was
353 -- created to accomplish the move.
354 -- p_new_object_version_number Yes number The object version number of the
355 -- 'new' position, ie. the position
356 -- which was created to accomplish
357 -- the move.
358 -- p_mass_move_id No number Where this Business Process is
359 -- being called as part of Mass
360 -- Move, this is the particular
361 -- mass move that is being
362 -- processed.
363 --
364 --
365 -- Post Success:
366 -- When the post-move position DML is successful, the following out
367 -- parameters are set :
368 -- Name Type Description
369 -- p_object_version_number number The object version number of the
370 -- 'old' position, ie. the position
371 -- which was moved.
372 -- p_new_object_version_number number The object version number of the
373 -- 'new' position, ie. the position
374 -- which was created to accomplish
375 -- the move.
376 --
377 -- Post Failure:
378 -- The API does not update the position(s) and raises an error.
379 --
380 -- Access Status:
381 -- Public.
382 --
383 -- {End Of Comments}
384 --
385 --
386 procedure post_move_position
387 (p_validate in boolean default false
388 ,p_position_id in number
389 ,p_object_version_number in out number
390 ,p_date_effective in date
391 ,p_business_group_id in number
392 ,p_organization_id in number
393 ,p_deactivate_old_position in boolean default false
394 ,p_new_position_id in number
395 ,p_new_object_version_number in out number
396 ,p_mass_move_id in number default hr_api.g_number
397 );
398 --
399 -- ----------------------------------------------------------------------------
400 -- |---------------------------< pre_mass_move >------------------------------|
401 -- ----------------------------------------------------------------------------
402 --
403 -- Description:
404 -- The pre-core mass move procedure is delivered as an 'empty'
405 -- packaged procedure which the customer can customize by coding any additional
406 -- validation which they may require before a mass move begins.
407 --
408 -- Prerequisites:
409 -- None.
410 --
411 --
412 -- In Parameters:
413 -- Name Reqd Type Description
414 -- p_mass_move_id Y number The ID of the mass move.
415 --
416 -- Post Success:
417 -- The pre-move validation has been successful, and processing by the
418 -- core mass_move process proceeds.
419 --
420 -- Post Failure:
421 -- The mass move has not been successfully validated for continuing and an
422 -- error is raised.
423 --
424 -- Access Status:
425 -- Public.
426 --
427 --
428 procedure pre_mass_move
429 (p_mass_move_id in number default hr_api.g_number
430 );
431 --
432 -- ----------------------------------------------------------------------------
433 -- |---------------------------< post_mass_move >-----------------------------|
434 -- ----------------------------------------------------------------------------
435 --
436 -- Description:
437 -- The post-core mass move procedure is delivered as an 'empty'
438 -- packaged procedure which the customer can customize by coding any additional
439 -- validation after a mass move has completed.
440 --
441 -- Prerequisites:
442 -- None.
443 --
444 -- In Parameters:
445 -- Name Reqd Type Description
446 -- p_mass_move_id Yes number The ID of the mass move
447 --
448 -- Post Success:
449 -- The entire mass move process completes.
450 --
451 -- Post Failure:
452 -- Errors are written to HR_API_BATCH_MESSAGE_LINES table.
453 --
454 -- Access Status:
455 -- Public.
456 --
457 --
458 procedure post_mass_move
459 (p_mass_move_id in number default hr_api.g_number
460 );
461 --
462 end hr_mass_move_cus ;
463 --
[Home] [Help]