1 Package hr_user_acct_bk2 AUTHID CURRENT_USER as
2 /* $Header: hrusrapi.pkh 120.5 2008/03/31 04:42:16 ubhat noship $ */
3 --
4 -- ----------------------------------------------------------------------------
5 -- | ------------------------ update_user_acct_b ---------------------------- |
6 -- | The update_user_acct api is strictly used for inactivating terminated |
7 -- | person's user account. The caller api does not gather any information |
8 -- | from the user hook program. |
9 -- | |
10 -- | NOTES: |
11 -- | p_person_id, p_per_effective_start_date, p_per_effective_end_date: |
12 -- | All 3 parameters are used together to uniquely retrieve person |
13 -- | record information from per_all_people_f table when the person |
14 -- | starts to become 'EX_EMP' in the person type. For example, if an |
15 -- | person is terminated on 31-Jan-2000,then p_per_effective_start_date |
16 -- | will have a value of 01-Feb-2000, that's when the person becomes |
17 -- | ex_person. |
18 -- | The SELECT statement should be something like: |
19 -- | *** Use "=" for the date comparision *** |
20 -- | Select ..... |
21 -- | from per_all_people_f ppf |
22 -- | where ppf.person_id = p_person_id |
23 -- | and ppf.effective_start_date = p_per_effective_start_date |
24 -- | and ppf.effective_end_date = p_per_effective_end_date |
25 -- | and ..... |
26 -- | |
27 -- | p_assignment_id, p_asg_effective_start_date, p_asg_effective_end_date: |
28 -- | All 3 parameters are used together to uniquely retrieve assignment |
29 -- | record information from per_all_assignments_f table when the person |
30 -- | assignment starts to become 'TERM_ASSIGN' in the assignment status |
31 -- | type. For example, if a person is terminated on 31-Jan-2000,then |
32 -- | p_asg_effective_start_date will have a value of 01-Feb-2000, that's |
33 -- | when the person's assignment becomes Terminate Assignment. |
34 -- | The SELECT statement should be something like: |
35 -- | *** Use "=" for the date comparision *** |
36 -- | Select ..... |
37 -- | from per_all_assignments paf |
38 -- | where paf.assignment_id = p_assignment_id |
39 -- | and paf.effective_start_date = p_asg_effective_start_date |
40 -- | and paf.effective_end_date = p_asg_effective_end_date |
41 -- | and ..... |
42 -- | |
43 -- | p_date_from, p_date_to: |
44 -- | The date comparison will be different depending on p_run_type. |
45 -- | Normally, in user hook program, the set of p_person_id and |
46 -- | p_assignment_id fields should be sufficient to retrieve person or |
47 -- | assignment record info. These two fields are provided so that the |
48 -- | user hook program knows what the person extract criteria are. |
49 -- | |
50 -- | p_org_structure_id, p_org_structure_vers_id, p_parent_org_id, |
51 -- | p_single_org_id, p_run_type - these parameters are provided for the |
52 -- | purpose of letting user hook program know what the person extract |
53 -- | criteria are. |
54 -- | |
55 -- | p_inactivate_date - The termination date. |
56 -- | |
57 -- ----------------------------------------------------------------------------
58 --
59 -- api user hooks - update_user_acct_b
60 --
61 PROCEDURE update_user_acct_b
62 (p_person_id in number
63 ,p_per_effective_start_date in date
64 ,p_per_effective_end_date in date
65 ,p_assignment_id in number
66 ,p_asg_effective_start_date in date
67 ,p_asg_effective_end_date in date
68 ,p_business_group_id in number
69 ,p_date_from in date
70 ,p_date_to in date
71 ,p_org_structure_id in number
72 ,p_org_structure_vers_id in number
73 ,p_parent_org_id in number
74 ,p_single_org_id in number
75 ,p_run_type in varchar2
76 ,p_inactivate_date in date
77 );
78
79 --
80 -- ----------------------------------------------------------------------------
81 -- | ------------------------ update_user_acct_a ---------------------------- |
82 -- | The update_user_acct api is strictly used for inactivating terminated |
83 -- | person's user account. The caller api does not gather any information |
84 -- | from the user hook program. |
85 -- | |
86 -- | NOTES: |
87 -- | p_person_id, p_per_effective_start_date, p_per_effective_end_date: |
88 -- | All 3 parameters are used together to uniquely retrieve person |
89 -- | record information from per_all_people_f table when the person |
90 -- | starts to become 'EX_EMP' in the person type. For example, if an |
91 -- | person is terminated on 31-Jan-2000,then p_per_effective_start_date |
92 -- | will have a value of 01-Feb-2000, that's when the person's person |
93 -- | type becomes ex_person. |
94 -- | The SELECT statement should be something like: |
95 -- | *** Use "=" for the date comparision *** |
96 -- | Select ..... |
97 -- | from per_all_people_f ppf |
98 -- | where ppf.person_id = p_person_id |
99 -- | and ppf.effective_start_date = p_per_effective_start_date |
100 -- | and ppf.effective_end_date = p_per_effective_end_date |
101 -- | and ..... |
102 -- | |
103 -- | p_assignment_id, p_asg_effective_start_date, p_asg_effective_end_date: |
104 -- | All 3 parameters are used together to uniquely retrieve assignment |
105 -- | record information from per_all_assignments_f table when the person |
106 -- | assignment starts to become 'TERM_ASSIGN' in the assignment status |
107 -- | type. For example, if a person is terminated on 31-Jan-2000,then |
108 -- | p_asg_effective_start_date will have a value of 01-Feb-2000, that's |
109 -- | when the person's assignment becomes Terminate Assignment. |
110 -- | The SELECT statement should be something like: |
111 -- | *** Use "=" for the date comparision *** |
112 -- | Select ..... |
113 -- | from per_all_assignments paf |
114 -- | where paf.assignment_id = p_assignment_id |
115 -- | and paf.effective_start_date = p_asg_effective_start_date |
116 -- | and paf.effective_end_date = p_asg_effective_end_date |
117 -- | and ..... |
118 -- | |
119 -- | p_date_from, p_date_to: |
120 -- | The date comparison will be different depending on p_run_type. |
121 -- | Normally, in user hook program, the set of p_person_id and |
122 -- | p_assignment_id fields should be sufficient to retrieve person or |
123 -- | assignment record info. These two fields are provided so that the |
124 -- | user hook program knows what the person extract criteria are. |
125 -- | |
126 -- | p_org_structure_id, p_org_structure_vers_id, p_parent_org_id, |
127 -- | p_single_org_id, p_run_type - these parameters are provided for the |
128 -- | purpose of letting user hook program know what the person extract |
129 -- | criteria are. |
130 -- | |
131 -- | p_inactivate_date - The termination date. |
132 -- | |
133 -- ----------------------------------------------------------------------------
134 -- api user hooks - update_user_acct_a
135 --
136 PROCEDURE update_user_acct_a
137 (p_person_id in number
138 ,p_per_effective_start_date in date
139 ,p_per_effective_end_date in date
140 ,p_assignment_id in number
141 ,p_asg_effective_start_date in date
142 ,p_asg_effective_end_date in date
143 ,p_business_group_id in number
144 ,p_date_from in date
145 ,p_date_to in date
146 ,p_org_structure_id in number
147 ,p_org_structure_vers_id in number
148 ,p_parent_org_id in number
149 ,p_single_org_id in number
150 ,p_run_type in varchar2
151 ,p_inactivate_date in date
152 );
153
154 --
155 END hr_user_acct_bk2;
[Home] [Help]