1 PACKAGE per_pds_utils AS
2 /* $Header: pepdsutl.pkh 120.1 2006/05/09 06:17:51 lsilveir noship $ */
3 --
4 -- ----------------------------------------------------------------------------
5 -- |-------------------------< Check_Move_Hire_Date >-------------------------|
6 -- ----------------------------------------------------------------------------
7 -- {Start Of Comments}
8 --
9 -- Description:
10 -- This business support process provides a hook for other product teams to
11 -- invoke their specific code to handle the change of hire date event.
12 --
13 -- Prerequisites:
14 -- The person assignments and periods of service must already be present.
15 --
16 -- In Parameters:
17 -- Name Reqd Type Description
18 -- p_person_id Yes number Identifier for the person
19 -- p_old_start_date Yes date Old Hire Date
20 -- p_new_start_date Yes date New Hire Date
21 -- p_type Yes varchar2 Type of person
22 --
23 -- Post Success:
24 -- No error is raised if the new hire date is valid
25 --
26 -- Post Failure:
27 -- An error is raised and control returned if the new hire date is not
28 -- valid.
29 --
30 -- Access Status:
31 -- For Oracle Internal use only.
32 --
33 -- {End Of Comments}
34 --
35 PROCEDURE check_move_hire_date
36 (p_person_id IN NUMBER
37 ,p_old_start_date IN DATE
38 ,p_new_start_date IN DATE
39 ,p_type IN VARCHAR2
40 );
41 --
42 -- ----------------------------------------------------------------------------
43 -- |----------------------------< Hr_Run_Alu_Ee >-----------------------------|
44 -- ----------------------------------------------------------------------------
45 -- {Start Of Comments}
46 --
47 -- Description:
48 -- This business support process provides a hook for the Payroll team to use
49 -- to invoke their new API to perform any processing that accounts for the
50 -- effect on Payroll Actions of changing hire date.
51 --
52 -- Prerequisites:
53 -- The person assignments and periods of service must already be present.
54 --
55 -- In Parameters:
56 -- Name Reqd Type Description
57 -- p_person_id Yes number Identifier for the person
58 -- p_old_start_date Yes date Old Hire Date
59 -- p_new_start_date Yes date New Hire Date
60 -- p_type Yes varchar2 Type of person
61 --
62 -- Post Success:
63 -- No error is raised if the new hire date is valid
64 --
65 -- Post Failure:
66 -- An error is raised and control returned if the new hire date is not
67 -- valid.
68 --
69 -- Access Status:
70 -- For Oracle Internal use only.
71 --
72 -- {End Of Comments}
73 --
74 PROCEDURE hr_run_alu_ee
75 (p_person_id IN NUMBER
76 ,p_old_start_date IN DATE
77 ,p_new_start_date IN DATE
78 ,p_type IN VARCHAR2
79 );
80 --
81 -- ----------------------------------------------------------------------------
82 -- |-----------------------< Move_Elements_With_Fpd >-------------------------|
83 -- ----------------------------------------------------------------------------
84 -- {Start Of Comments}
85 --
86 -- Description:
87 -- This business procedure provides a hook for the Payroll team to use
88 -- to invoke their new API to handle the updation of element entries in
89 -- sync with changes to FPD.
90 --
91 -- Prerequisites:
92 -- The person assignments and periods of service must already be present.
93 --
94 -- In Parameters:
95 -- Name Reqd Type Description
96 -- p_assignment_id Yes number Assignment Identifier
97 -- p_periods_of_service_id Yes number Period Of Service Identifier
98 -- p_old_final_process_date Yes date Old Final Process Date
99 -- p_new_final_process_date Yes date New Final Process Date
100 --
101 -- Post Success:
102 -- Dates for both recurring and non-recurring element entries are in sync
103 -- with the new FPD
104 --
105 -- Post Failure:
106 -- An error is raised and control returned
107 --
108 -- Access Status:
109 -- For Oracle Internal use only.
110 --
111 -- {End Of Comments}
112 --
113 PROCEDURE move_elements_with_fpd
114 (p_assignment_id IN NUMBER
115 ,p_periods_of_service_id IN NUMBER
116 ,p_old_final_process_date IN DATE
117 ,p_new_final_process_date IN DATE
118 );
119 --
120 END per_pds_utils;
[Home] [Help]