1 Package hr_user_acct_bk1 AUTHID CURRENT_USER as
2 /* $Header: hrusrapi.pkh 120.5 2008/03/31 04:42:16 ubhat noship $ */
3 --
4 -- ----------------------------------------------------------------------------
5 -- |--------------------------< create_user_acct_b >--------------------------|
6 -- | |
7 -- | NOTES: |
8 -- | p_person_id, p_per_effective_start_date, p_per_effective_end_date: |
9 -- | All 3 parameters are used together to uniquely retrieve person |
10 -- | record information from per_all_people_f table. |
11 -- | The SELECT statement should be something like: |
12 -- | *** Use "=" for the date comparision *** |
13 -- | Select ..... |
14 -- | from per_all_people_f ppf |
15 -- | where ppf.person_id = p_person_id |
16 -- | and ppf.effective_start_date = p_per_effective_start_date |
17 -- | and ppf.effective_end_date = p_per_effective_end_date |
18 -- | and ..... |
19 -- | |
20 -- | p_assignment_id, p_asg_effective_start_date, p_asg_effective_end_date: |
21 -- | All 3 parameters are used together to uniquely retrieve assignment |
22 -- | record information from per_all_assignments_f table. |
23 -- | The SELECT statement should be something like: |
24 -- | *** Use "=" for the date comparision *** |
25 -- | Select ..... |
26 -- | from per_all_assignments paf |
27 -- | where paf.assignment_id = p_assignment_id |
28 -- | and paf.effective_start_date = p_asg_effective_start_date |
29 -- | and paf.effective_end_date = p_asg_effective_end_date |
30 -- | and ..... |
31 -- | |
32 -- | p_date_from, p_date_to: |
33 -- | The date comparison will be different depending on p_run_type. |
34 -- | Normally, in user hook program, the set of p_person_id and |
35 -- | p_assignment_id fields should be sufficient to retrieve person or |
36 -- | assignment record info. These two fields are provided so that the |
37 -- | user hook program knows what the person extract criteria are. |
38 -- | |
39 -- | p_org_structure_id, p_org_structure_vers_id, p_parent_org_id, |
40 -- | p_single_org_id, p_run_type - these parameters are provided for the |
41 -- | purpose of letting user hook program know what the person extract |
42 -- | criteria are. |
43 -- | |
44 -- | p_hire_date - This date is provided so that the user hook program can |
45 -- | decide what the start date should be for the new user record. |
46 -- | Usually the start date for a new hire's user account should be the |
47 -- | hire date. However, the user hook program can supply any date but |
48 -- | not before the hire date. |
49 -- | |
50 -- ----------------------------------------------------------------------------
51 -- api user hooks - create_user_acct_b
52 PROCEDURE create_user_acct_b
53 (p_person_id in number
54 ,p_per_effective_start_date in date
55 ,p_per_effective_end_date in date
56 ,p_assignment_id in number
57 ,p_asg_effective_start_date in date
58 ,p_asg_effective_end_date in date
59 ,p_business_group_id in number
60 ,p_date_from in date
61 ,p_date_to in date
62 ,p_org_structure_id in number
63 ,p_org_structure_vers_id in number
64 ,p_parent_org_id in number
65 ,p_single_org_id in number
66 ,p_run_type in varchar2
67 ,p_hire_date in date
68 );
69 --
70 -- ----------------------------------------------------------------------------
71 -- |--------------------------< create_user_acct_a >--------------------------|
72 -- | This user hook is used for saving automatically generated password |
73 -- | information by the user hook program. |
74 -- | |
75 -- | NOTES: |
76 -- | p_person_id, p_per_effective_start_date, p_per_effective_end_date: |
77 -- | All 3 parameters are used together to uniquely retrieve person |
78 -- | record information from per_all_people_f table. |
79 -- | The SELECT statement should be something like: |
80 -- | *** Use "=" for the date comparision *** |
81 -- | Select ..... |
82 -- | from per_all_people_f ppf |
83 -- | where ppf.person_id = p_person_id |
84 -- | and ppf.effective_start_date = p_per_effective_start_date |
85 -- | and ppf.effective_end_date = p_per_effective_end_date |
86 -- | and ..... |
87 -- | |
88 -- | p_assignment_id, p_asg_effective_start_date, p_asg_effective_end_date: |
89 -- | All 3 parameters are used together to uniquely retrieve assignment |
90 -- | record information from per_all_assignments_f table. |
91 -- | The SELECT statement should be something like: |
92 -- | *** Use "=" for the date comparision *** |
93 -- | Select ..... |
94 -- | from per_all_assignments paf |
95 -- | where paf.assignment_id = p_assignment_id |
96 -- | and paf.effective_start_date = p_asg_effective_start_date |
97 -- | and paf.effective_end_date = p_asg_effective_end_date |
98 -- | and ..... |
99 -- | |
100 -- | p_date_from, p_date_to: |
101 -- | The date comparison will be different depending on p_run_type. |
102 -- | Normally, in user hook program, the set of p_person_id and |
103 -- | p_assignment_id fields should be sufficient to retrieve person or |
104 -- | assignment record info. These two fields are provided so that the |
105 -- | user hook program knows what the person extract criteria are. |
106 -- | |
107 -- | p_org_structure_id, p_org_structure_vers_id, p_parent_org_id, |
108 -- | p_single_org_id, p_run_type - these parameters are provided for the |
109 -- | purpose of letting user hook program know what the person extract |
110 -- | criteria are. |
111 -- | |
112 -- | p_hire_date - This date is provided so that the user hook program can |
113 -- | decide what the start date should be for the new user record. |
114 -- | Usually the start date for a new hire's user account should be the |
115 -- | hire date. However, the user hook program can supply any date but |
116 -- | not before the hire date. |
117 -- | |
118 -- ----------------------------------------------------------------------------
119 -- api user hooks - create_user_acct_a
120 PROCEDURE create_user_acct_a
121 (p_person_id in number
122 ,p_per_effective_start_date in date
123 ,p_per_effective_end_date in date
124 ,p_assignment_id in number
125 ,p_asg_effective_start_date in date
126 ,p_asg_effective_end_date in date
127 ,p_business_group_id in number
128 ,p_date_from in date
129 ,p_date_to in date
130 ,p_org_structure_id in number
131 ,p_org_structure_vers_id in number
132 ,p_parent_org_id in number
133 ,p_single_org_id in number
134 ,p_run_type in varchar2
135 ,p_hire_date in date
136 );
137 --
138 END hr_user_acct_bk1;
[Home] [Help]