1 Package ben_process_user_utility AUTHID CURRENT_USER AS
2 /* $Header: benusrgb.pkh 115.1 2002/02/13 06:40:55 pkm ship $ */
3 --
4 -- Public Global Variables
5 --
6 g_package varchar2(33) := 'ben_process_user_utility.';
7 --
8 -- ----------------------------------------------------------------------------
9 -- NOTE: This package specification contains global variables only. It does
10 -- not have any functions or procedures. The purpose of this specification
11 -- is to allow user hooks to communicate output information to the caller
12 -- api.
13 -- ----------------------------------------------------------------------------
14 -- USAGE NOTES FOR CREATING A USER NAME:
15 -- user_name - required, cannot be more than 100 characters.
16 --
17 -- password - optional. If entered, the length cannot be more than the
18 -- length in SIGNON_PASSWORD_LENGTH profile option. If null
19 -- value, a randomly generated 8-byte alphanumeric string will be
20 -- generated.
21 --
22 -- start_date - optional. If null value, Today's Date will be
23 -- used.
24 --
25 -- end_date - optional. If entered, it must be greater than start_date.
26 --
27 -- last_logon_date - optional. The date the user last signed on. Suggestion: Take Default.
28 --
29 -- password_date - optional. The date the current password was set. Suggestion: Take Default(Should never pass null).
30 --
31 -- password_accesses_left - optional. The number of accesses left for the password.Suggestion: Take Default.
32 --
33 -- password_lifespan_accesses - optional. No. of Accesses allowed for the password. Suggestion: Take Default.
34 --
35 -- p_password_lifespan_days - optional. Lifespan of the password. Suggestion: Take Default.
36 --
37 -- email_address - optional. If entered, cannot be more than 240 characters.
38 --
39 -- fax - optional. If entered, cannot be more than 80 characters.
40 --
41 -- description - optional. If entered, cannot be more than 240 characters.
42 --
43 -- employee_id - optional. If the user name is to associate to an employee,
44 -- then this field must contain a valid person_id in
45 -- per_all_people_f table.
46 --
47 -- customer_id - optional. No validation is done on this field. This field
48 -- is used by non Oracle Human Resources Application and this
49 -- program is intended for HR Application use only.
50 --
51 -- supplier_id - optional. No validation is done on this field. This field
52 -- is used by non Oracle Human Resources Application and this
53 -- program is intended for HR Application use only.
54 -----------------------------------------------------------------------------------
55 --
56 --RECORD STRUCTURE FOR FND_USERS
57 -- ==============================
58 TYPE fnd_user_record IS RECORD
59 (user_name fnd_user.user_name%type
60 ,password varchar2(30)
61 ,start_date fnd_user.start_date%type
62 ,end_date fnd_user.end_date%type
63 ,last_logon_date fnd_user.last_logon_date%type
64 ,password_date fnd_user.password_date%type
65 ,password_accesses_left fnd_user.password_accesses_left%type
66 ,password_lifespan_accesses fnd_user.password_lifespan_accesses%type
67 ,password_lifespan_days fnd_user.password_lifespan_days%type
68 ,email_address fnd_user.email_address%type
69 ,fax fnd_user.fax%type
70 ,description fnd_user.description%type
71 ,employee_id fnd_user.employee_id%type
72 ,customer_id fnd_user.customer_id%type
73 ,supplier_id fnd_user.supplier_id%type
74 );
75 --
76 g_fnd_user_record fnd_user_record;
77 --
78 --
79 -- ----------------------------------------------------------------------------
80 -- USAGE NOTES FOR CREATING/UPDATING A RESPONSIBILTY, ASSOCIATING A
81 -- RESPONSIBILITY, SECURITY GROUP TO A USERNAME:
82 --
83 -- ***************************************************************************
84 -- If the profile option 'ENABLE_SECURITY_GROUPS' for the Application is 'Y',
85 -- then you'll need to populate the sec_group_id, sec_profile_id fields at the
86 -- end of this record structure. The system will insert a row into
87 -- per_sec_profile_assignments as well as to fnd_user_resp_groups.
88 --
89 -- If the profile option 'ENABLE_SECURITY_GROUPS' for the Application is 'N',
90 -- that means you remain to use the R11 way of responsibility and security profile
91 -- set up. There is no need to fill in the values of sec_group_id and
92 -- sec_profile_id fields. The system will insert a row into fnd_user_resp_groups
93 -- only.
94 --***************************************************************************
95 --
96 -- responsibility_id - should never exceed length of
97 -- fnd_responsibility.responsibility_id value(which is 15).
98 --
99 -- respons_application_id - cannot exceed the length of
100 -- fnd_responsibility.application_id, which is a number type
101 -- with a size of 15.
102 --
103 -- security_group_id -optional for 'ENABLE_SECURITY_GROUPS' profile option =
104 -- 'Y'. Length cannot exceed
105 -- per_sec_profile_assignments.security_group_id, which is
106 -- a number data type. It must be a valid value in
107 -- fnd_security_groups.security_group_id.
108 -- If this field is null or sec_profile_id is null,
109 -- then the view-all security profile for the employee's
110 -- business group will be used. No row will be inserted
111 -- into per_security_profile_assignments. Only 1 row will
112 -- be inserted into fnd_user_resp_groups table.
113 -- If 'ENABLE_SECURITY_GROUPS' profile option = 'N', leave
114 -- this field null.
115 --
116 -- sec_profile_id - optional for 'ENABLE_SECURITY_GROUPS' profile option
117 -- = 'Y'. Length cannot exceed
118 -- per_sec_profile_assignments.security_profile_id, which is
119 -- a number data type. It must be a valid value in
120 -- per_security_profiles.security_profile_id.
121 -- If this field is null or sec_profile_id is null,
122 -- then the view-all security profile for the employee's
123 -- business group will be used. No row will be inserted
124 -- into per_security_profile_assignments. Only 1 row will
125 -- be inserted into fnd_user_resp_groups table.
126 -- If 'ENABLE_SECURITY_GROUPS' profile option = 'N', leave
127 -- this field null.
128 --
129 ----------------------------------------------------------------------------
130 --RECORD STRUCTURE FOR FND_RESPONSIBILITIES
131 -- =========================================
132 TYPE fnd_resp_record IS RECORD
133 (responsibility_id fnd_responsibility.responsibility_id%type
134 ,respons_application_id fnd_responsibility.application_id%type
135 ,security_group_id fnd_security_groups.security_group_id%type
136 ,security_profile_id per_sec_profile_assignments.security_profile_id%type
137 );
138 g_fnd_resp_record fnd_resp_record;
139 --
140 end ben_process_user_utility;