[Home] [Help]
5: --
6: --
7: g_package varchar2(33) := 'hr_user_acct_api.';
8: g_api_vers constant number := 1.0;
9: g_empty_fnd_user_rec hr_user_acct_utility.fnd_user_rec;
10: g_emtpy_fnd_resp_tbl hr_user_acct_utility.fnd_responsibility_tbl;
11: g_emtpy_fnd_prof_opt_val_tbl hr_user_acct_utility.fnd_profile_opt_val_tbl;
12: g_empty_fnd_resp_func_tbl hr_user_acct_utility.fnd_resp_functions_tbl;
13: g_empty_func_sec_excl_tbl hr_user_acct_utility.func_sec_excl_tbl;
94: l_hire_date date default null;
95: l_date_from date default null;
96: l_date_to date default null;
97: --
98: l_user_name fnd_user.user_name%type default null;
99: l_fnd_user_start_date fnd_user.start_date%type default null;
100: l_fnd_user_end_date fnd_user.end_date%type default null;
101: l_email_address fnd_user.email_address%type default null;
102: l_fax fnd_user.email_address%type default null;
95: l_date_from date default null;
96: l_date_to date default null;
97: --
98: l_user_name fnd_user.user_name%type default null;
99: l_fnd_user_start_date fnd_user.start_date%type default null;
100: l_fnd_user_end_date fnd_user.end_date%type default null;
101: l_email_address fnd_user.email_address%type default null;
102: l_fax fnd_user.email_address%type default null;
103: l_customer_id fnd_user.customer_id%type default null;
96: l_date_to date default null;
97: --
98: l_user_name fnd_user.user_name%type default null;
99: l_fnd_user_start_date fnd_user.start_date%type default null;
100: l_fnd_user_end_date fnd_user.end_date%type default null;
101: l_email_address fnd_user.email_address%type default null;
102: l_fax fnd_user.email_address%type default null;
103: l_customer_id fnd_user.customer_id%type default null;
104: l_description fnd_user.description%type default null;
97: --
98: l_user_name fnd_user.user_name%type default null;
99: l_fnd_user_start_date fnd_user.start_date%type default null;
100: l_fnd_user_end_date fnd_user.end_date%type default null;
101: l_email_address fnd_user.email_address%type default null;
102: l_fax fnd_user.email_address%type default null;
103: l_customer_id fnd_user.customer_id%type default null;
104: l_description fnd_user.description%type default null;
105: l_language fnd_profile_option_values.profile_option_value%type
98: l_user_name fnd_user.user_name%type default null;
99: l_fnd_user_start_date fnd_user.start_date%type default null;
100: l_fnd_user_end_date fnd_user.end_date%type default null;
101: l_email_address fnd_user.email_address%type default null;
102: l_fax fnd_user.email_address%type default null;
103: l_customer_id fnd_user.customer_id%type default null;
104: l_description fnd_user.description%type default null;
105: l_language fnd_profile_option_values.profile_option_value%type
106: default null;
99: l_fnd_user_start_date fnd_user.start_date%type default null;
100: l_fnd_user_end_date fnd_user.end_date%type default null;
101: l_email_address fnd_user.email_address%type default null;
102: l_fax fnd_user.email_address%type default null;
103: l_customer_id fnd_user.customer_id%type default null;
104: l_description fnd_user.description%type default null;
105: l_language fnd_profile_option_values.profile_option_value%type
106: default null;
107: l_user_id number default null;
100: l_fnd_user_end_date fnd_user.end_date%type default null;
101: l_email_address fnd_user.email_address%type default null;
102: l_fax fnd_user.email_address%type default null;
103: l_customer_id fnd_user.customer_id%type default null;
104: l_description fnd_user.description%type default null;
105: l_language fnd_profile_option_values.profile_option_value%type
106: default null;
107: l_user_id number default null;
108: --
108: --
109: l_fnd_resp_rec hr_user_acct_utility.fnd_responsibility_rec;
110: l_responsibility_id fnd_responsibility.responsibility_id%type := null;
111: l_responsibility_key fnd_responsibility.responsibility_key%type := null;
112: l_user_resp_start_date fnd_user_resp_groups.start_date%type;
113: l_user_resp_end_date fnd_user_resp_groups.end_date%type;
114: l_user_level_only boolean default false;
115: l_count number default 0;
116: l_prof_opt_val_count number default 0;
109: l_fnd_resp_rec hr_user_acct_utility.fnd_responsibility_rec;
110: l_responsibility_id fnd_responsibility.responsibility_id%type := null;
111: l_responsibility_key fnd_responsibility.responsibility_key%type := null;
112: l_user_resp_start_date fnd_user_resp_groups.start_date%type;
113: l_user_resp_end_date fnd_user_resp_groups.end_date%type;
114: l_user_level_only boolean default false;
115: l_count number default 0;
116: l_prof_opt_val_count number default 0;
117: l_resp_count number default 0;
145: begin
146: -- Clear the global record table variables first. Otherwise,these variables
147: -- will retain values from the previous employee.
148: --
149: hr_user_acct_utility.g_fnd_user_rec := g_empty_fnd_user_rec;
150: hr_user_acct_utility.g_fnd_resp_tbl := g_emtpy_fnd_resp_tbl;
151: hr_user_acct_utility.g_fnd_profile_opt_val_tbl :=
152: g_emtpy_fnd_prof_opt_val_tbl;
153: hr_user_acct_utility.g_fnd_resp_functions_tbl :=
158: -- per_all_people_f.effective_end_date along with the concurrent
159: -- program's input parameters are passed to the user hooks so
160: -- that the user can retrieve the proper person record or
161: -- assignment record to determine what user name, password and
162: -- the start date for the fnd_users account. Normally, the start
163: -- date for the fnd_users account is the hire date. But the user
164: -- can change it to a later date but not earlier in their user hooks code.
165: --
166: -- Users should use the create_user_acct_b user hook to
159: -- program's input parameters are passed to the user hooks so
160: -- that the user can retrieve the proper person record or
161: -- assignment record to determine what user name, password and
162: -- the start date for the fnd_users account. Normally, the start
163: -- date for the fnd_users account is the hire date. But the user
164: -- can change it to a later date but not earlier in their user hooks code.
165: --
166: -- Users should use the create_user_acct_b user hook to
167: -- return username, password, responsibilities and profile option values.
195: (p_module_name => 'CREATE_USER_ACCOUNT'
196: ,p_hook_type => 'BP'
197: );
198: --
199: -- End of API User Hook for the before hook of create_fnd_user_resp
200: --
201: end;
202: --
203: --
208: -- NOTE: User hooks can pass information back to us, such as user name,
209: -- password, responsibilities and profile info. via global variables
210: -- in the dummy hr_user_acct_utility package header. We directly
211: -- move information from there to the parameters in
212: -- create_fnd_user. Validations will be done in individual business
213: -- process, such as create_fnd_user, not at the wrapper level.
214: --
215: -----------------------------------------------------------------------------
216: --
209: -- password, responsibilities and profile info. via global variables
210: -- in the dummy hr_user_acct_utility package header. We directly
211: -- move information from there to the parameters in
212: -- create_fnd_user. Validations will be done in individual business
213: -- process, such as create_fnd_user, not at the wrapper level.
214: --
215: -----------------------------------------------------------------------------
216: --
217: -- In R11.5, the java program no longer needs the host port information since
220: -- null value to the parameter.
221: --
222:
223: -- Fix 2288014.
224: -- Passing password_date to the modified hr_user_acct_internal.create_fnd_user
225: -- enabling users to have control over password change after first login.
226: --
227: hr_user_acct_internal.create_fnd_user
228: (p_hire_date => l_hire_date
223: -- Fix 2288014.
224: -- Passing password_date to the modified hr_user_acct_internal.create_fnd_user
225: -- enabling users to have control over password change after first login.
226: --
227: hr_user_acct_internal.create_fnd_user
228: (p_hire_date => l_hire_date
229: ,p_user_name =>
230: hr_user_acct_utility.g_fnd_user_rec.user_name
231: ,p_password =>
226: --
227: hr_user_acct_internal.create_fnd_user
228: (p_hire_date => l_hire_date
229: ,p_user_name =>
230: hr_user_acct_utility.g_fnd_user_rec.user_name
231: ,p_password =>
232: hr_user_acct_utility.g_fnd_user_rec.password
233: ,p_user_start_date =>
234: hr_user_acct_utility.g_fnd_user_rec.start_date
228: (p_hire_date => l_hire_date
229: ,p_user_name =>
230: hr_user_acct_utility.g_fnd_user_rec.user_name
231: ,p_password =>
232: hr_user_acct_utility.g_fnd_user_rec.password
233: ,p_user_start_date =>
234: hr_user_acct_utility.g_fnd_user_rec.start_date
235: ,p_user_end_date =>
236: hr_user_acct_utility.g_fnd_user_rec.end_date
230: hr_user_acct_utility.g_fnd_user_rec.user_name
231: ,p_password =>
232: hr_user_acct_utility.g_fnd_user_rec.password
233: ,p_user_start_date =>
234: hr_user_acct_utility.g_fnd_user_rec.start_date
235: ,p_user_end_date =>
236: hr_user_acct_utility.g_fnd_user_rec.end_date
237: ,p_email_address =>
238: hr_user_acct_utility.g_fnd_user_rec.email_address
232: hr_user_acct_utility.g_fnd_user_rec.password
233: ,p_user_start_date =>
234: hr_user_acct_utility.g_fnd_user_rec.start_date
235: ,p_user_end_date =>
236: hr_user_acct_utility.g_fnd_user_rec.end_date
237: ,p_email_address =>
238: hr_user_acct_utility.g_fnd_user_rec.email_address
239: ,p_fax =>
240: hr_user_acct_utility.g_fnd_user_rec.fax
234: hr_user_acct_utility.g_fnd_user_rec.start_date
235: ,p_user_end_date =>
236: hr_user_acct_utility.g_fnd_user_rec.end_date
237: ,p_email_address =>
238: hr_user_acct_utility.g_fnd_user_rec.email_address
239: ,p_fax =>
240: hr_user_acct_utility.g_fnd_user_rec.fax
241: ,p_description =>
242: hr_user_acct_utility.g_fnd_user_rec.description
236: hr_user_acct_utility.g_fnd_user_rec.end_date
237: ,p_email_address =>
238: hr_user_acct_utility.g_fnd_user_rec.email_address
239: ,p_fax =>
240: hr_user_acct_utility.g_fnd_user_rec.fax
241: ,p_description =>
242: hr_user_acct_utility.g_fnd_user_rec.description
243: ,p_password_date =>
244: hr_user_acct_utility.g_fnd_user_rec.password_date -- Fix 2288014
238: hr_user_acct_utility.g_fnd_user_rec.email_address
239: ,p_fax =>
240: hr_user_acct_utility.g_fnd_user_rec.fax
241: ,p_description =>
242: hr_user_acct_utility.g_fnd_user_rec.description
243: ,p_password_date =>
244: hr_user_acct_utility.g_fnd_user_rec.password_date -- Fix 2288014
245: ,p_language =>
246: hr_user_acct_utility.g_fnd_user_rec.language
240: hr_user_acct_utility.g_fnd_user_rec.fax
241: ,p_description =>
242: hr_user_acct_utility.g_fnd_user_rec.description
243: ,p_password_date =>
244: hr_user_acct_utility.g_fnd_user_rec.password_date -- Fix 2288014
245: ,p_language =>
246: hr_user_acct_utility.g_fnd_user_rec.language
247: ,p_host_port => null
248: ,p_employee_id =>
242: hr_user_acct_utility.g_fnd_user_rec.description
243: ,p_password_date =>
244: hr_user_acct_utility.g_fnd_user_rec.password_date -- Fix 2288014
245: ,p_language =>
246: hr_user_acct_utility.g_fnd_user_rec.language
247: ,p_host_port => null
248: ,p_employee_id =>
249: hr_user_acct_utility.g_fnd_user_rec.employee_id
250: ,p_customer_id =>
245: ,p_language =>
246: hr_user_acct_utility.g_fnd_user_rec.language
247: ,p_host_port => null
248: ,p_employee_id =>
249: hr_user_acct_utility.g_fnd_user_rec.employee_id
250: ,p_customer_id =>
251: hr_user_acct_utility.g_fnd_user_rec.customer_id
252: ,p_supplier_id =>
253: hr_user_acct_utility.g_fnd_user_rec.supplier_id
247: ,p_host_port => null
248: ,p_employee_id =>
249: hr_user_acct_utility.g_fnd_user_rec.employee_id
250: ,p_customer_id =>
251: hr_user_acct_utility.g_fnd_user_rec.customer_id
252: ,p_supplier_id =>
253: hr_user_acct_utility.g_fnd_user_rec.supplier_id
254: ,p_user_id => l_user_id
255: );
249: hr_user_acct_utility.g_fnd_user_rec.employee_id
250: ,p_customer_id =>
251: hr_user_acct_utility.g_fnd_user_rec.customer_id
252: ,p_supplier_id =>
253: hr_user_acct_utility.g_fnd_user_rec.supplier_id
254: ,p_user_id => l_user_id
255: );
256: --
257: hr_utility.set_location(l_proc, 30);
260: --
261: l_resp_count := hr_user_acct_utility.g_fnd_resp_tbl.count;
262: --
263: IF l_resp_count < 1
264: -- No fnd_user_resp_groups, per_sec_profile_assignments,
265: -- function exclusions or profile option values to insert
266: THEN
267: goto after_process_hook;
268: END IF;
368: hr_api.g_number
369: THEN
370: l_fnd_resp_rec.new_resp_app_id :=
371: hr_user_acct_utility.g_fnd_resp_tbl(i).new_resp_app_id;
372: -- Set the application_id for fnd_user_resp_groups to
373: -- the new resp app id
374: l_user_resp_app_id :=
375: hr_user_acct_utility.g_fnd_resp_tbl(i).new_resp_app_id;
376: ELSE
373: -- the new resp app id
374: l_user_resp_app_id :=
375: hr_user_acct_utility.g_fnd_resp_tbl(i).new_resp_app_id;
376: ELSE
377: -- Set the application_id for fnd_user_resp_groups to
378: -- the template responsibility's app id
379: l_user_resp_app_id := l_fnd_resp_rec.new_resp_app_id;
380: END IF;
381: --
526:
527: IF l_enable_sec_groups = 'N'
528: THEN
529: hr_utility.set_location (l_proc ||
530: ' before create_fnd_user_resp_groups', 50);
531: --
532: -- **********************************************
533: -- Create the new fnd_user_resp_groups record
534: -- **********************************************
529: hr_utility.set_location (l_proc ||
530: ' before create_fnd_user_resp_groups', 50);
531: --
532: -- **********************************************
533: -- Create the new fnd_user_resp_groups record
534: -- **********************************************
535: -- NOTE: Only insert a row into fnd_user_resp_groups
536: -- when the profile option 'ENABLE_SECURITY_GROUPS'
537: -- is 'N'.
531: --
532: -- **********************************************
533: -- Create the new fnd_user_resp_groups record
534: -- **********************************************
535: -- NOTE: Only insert a row into fnd_user_resp_groups
536: -- when the profile option 'ENABLE_SECURITY_GROUPS'
537: -- is 'N'.
538: --
539: hr_user_acct_internal.create_fnd_user_resp_groups
535: -- NOTE: Only insert a row into fnd_user_resp_groups
536: -- when the profile option 'ENABLE_SECURITY_GROUPS'
537: -- is 'N'.
538: --
539: hr_user_acct_internal.create_fnd_user_resp_groups
540: (p_user_id => l_user_id
541: ,p_responsibility_id => l_responsibility_id
542: ,p_application_id => l_user_resp_app_id
543: ,p_sec_group_id => 0
546: ,p_description => l_fnd_resp_rec.user_resp_description
547: );
548:
549: hr_utility.set_location (l_proc ||
550: ' after create_fnd_user_resp_groups', 51);
551: ELSE
552: -- 'ENABLE_SECURITY_GROUPS' = 'Y'; customers have the option to insert
553: -- into fnd_user_resp_groups only if view-all security profile of the
554: -- employee's business group is to be used. This will be applicable
549: hr_utility.set_location (l_proc ||
550: ' after create_fnd_user_resp_groups', 51);
551: ELSE
552: -- 'ENABLE_SECURITY_GROUPS' = 'Y'; customers have the option to insert
553: -- into fnd_user_resp_groups only if view-all security profile of the
554: -- employee's business group is to be used. This will be applicable
555: -- to Employee Self Service responsibility. If a restricted security
556: -- profile is to be used, then we must call hrasprhi.pkb which will
557: -- insert one row into per_sec_profile_assignments as well as to
554: -- employee's business group is to be used. This will be applicable
555: -- to Employee Self Service responsibility. If a restricted security
556: -- profile is to be used, then we must call hrasprhi.pkb which will
557: -- insert one row into per_sec_profile_assignments as well as to
558: -- fnd_user_resp_groups.
559:
560: IF l_fnd_resp_rec.sec_group_id IS NULL OR
561: l_fnd_resp_rec.sec_profile_id IS NULL
562: THEN
559:
560: IF l_fnd_resp_rec.sec_group_id IS NULL OR
561: l_fnd_resp_rec.sec_profile_id IS NULL
562: THEN
563: -- Insert into fnd_user_resp_groups only
564: -- get the security_group_id for the employee's business_group_id
565:
566: OPEN lc_get_sec_group_id;
567: FETCH lc_get_sec_group_id into l_sec_group_id;
577: CLOSE lc_get_sec_group_id;
578: END IF;
579:
580: hr_utility.set_location (l_proc ||
581: ' before create_fnd_user_resp_groups', 53);
582: --
583: hr_user_acct_internal.create_fnd_user_resp_groups
584: (p_user_id => l_user_id
585: ,p_responsibility_id => l_responsibility_id
579:
580: hr_utility.set_location (l_proc ||
581: ' before create_fnd_user_resp_groups', 53);
582: --
583: hr_user_acct_internal.create_fnd_user_resp_groups
584: (p_user_id => l_user_id
585: ,p_responsibility_id => l_responsibility_id
586: ,p_application_id => l_user_resp_app_id
587: ,p_sec_group_id => l_sec_group_id
590: ,p_description => l_fnd_resp_rec.user_resp_description
591: );
592:
593: hr_utility.set_location (l_proc ||
594: ' after create_fnd_user_resp_groups', 54);
595: --
596: ELSE
597: -- sec_group_id and sec_profile_id are filled in
598: -- call peasprhi.pkb to insert into per_sec_profile_assignments
595: --
596: ELSE
597: -- sec_group_id and sec_profile_id are filled in
598: -- call peasprhi.pkb to insert into per_sec_profile_assignments
599: -- as well as fnd_user_resp_groups.
600:
601: hr_utility.set_location (l_proc ||
602: ' before create_sec_profile_asg', 56);
603:
954: ---------------------------------------------------------------------------
955: -- NOTE:
956: -- In R11.5, the java program WebSessionManager.class is now a stored
957: -- procedure on the database. It is being executed as part of the
958: -- transaction. When we rollback, the initial fnd_user record created by
959: -- the java program will also be rolled back. We no longer need to
960: -- remove the dangling fnd_user manually.
961: ---------------------------------------------------------------------------
962: --
956: -- In R11.5, the java program WebSessionManager.class is now a stored
957: -- procedure on the database. It is being executed as part of the
958: -- transaction. When we rollback, the initial fnd_user record created by
959: -- the java program will also be rolled back. We no longer need to
960: -- remove the dangling fnd_user manually.
961: ---------------------------------------------------------------------------
962: --
963: -- Only set output warning arguments
964: -- (Any key or derived arguments must be set to null
977: ---------------------------------------------------------------------------
978: -- NOTE:
979: -- In R11.5, the java program WebSessionManager.class is now a stored
980: -- procedure on the database. It is being executed as part of the
981: -- transaction. When we rollback, the initial fnd_user record created by
982: -- the java program will also be rolled back. We no longer need to
983: -- remove the dangling fnd_user manually.
984: ---------------------------------------------------------------------------
985: --
979: -- In R11.5, the java program WebSessionManager.class is now a stored
980: -- procedure on the database. It is being executed as part of the
981: -- transaction. When we rollback, the initial fnd_user record created by
982: -- the java program will also be rolled back. We no longer need to
983: -- remove the dangling fnd_user manually.
984: ---------------------------------------------------------------------------
985: --
986: p_user_id := null;
987: raise;
993: -- |-------------------------- < update_user_acct > --------------------------|
994: -- | |
995: -- | USAGE: |
996: -- | ----- |
997: -- | This wrapper module is used to update fnd_user and |
998: -- | fnd_user_resp_groups, or per_sec_profile_assignments records specifically|
999: -- | for expiring a user account. |
1000: -- | User accounts for terminated employees will not be deleted because |
1001: -- | some HR history forms have sql statements join to the fnd_user table |
994: -- | |
995: -- | USAGE: |
996: -- | ----- |
997: -- | This wrapper module is used to update fnd_user and |
998: -- | fnd_user_resp_groups, or per_sec_profile_assignments records specifically|
999: -- | for expiring a user account. |
1000: -- | User accounts for terminated employees will not be deleted because |
1001: -- | some HR history forms have sql statements join to the fnd_user table |
1002: -- | derive the who columns. |
997: -- | This wrapper module is used to update fnd_user and |
998: -- | fnd_user_resp_groups, or per_sec_profile_assignments records specifically|
999: -- | for expiring a user account. |
1000: -- | User accounts for terminated employees will not be deleted because |
1001: -- | some HR history forms have sql statements join to the fnd_user table |
1002: -- | derive the who columns. |
1003: -- ----------------------------------------------------------------------------
1004: --
1005: PROCEDURE update_user_acct
1027: --
1028: CURSOR lc_get_user_id
1029: IS
1030: SELECT user_id
1031: FROM fnd_user
1032: WHERE employee_id = p_person_id
1033: AND nvl(end_date, hr_api.g_eot) > l_date;
1034: --
1035: -- Cursor to select all records which belongs to the terminated employee's
1052: -- Cursor to select all records which belongs to the terminated employee's
1053: -- user id and the end date is null or the end date is greater than the
1054: -- termination date.
1055: --
1056: -- Fix for bug 4147802 starts here. used fnd_user_resp_groups_direct view
1057: -- in place of fnd_user_resp_groups. Also the column description is removed.
1058: --
1059: CURSOR lc_get_user_resp (c_user_id in number)
1060: IS
1053: -- user id and the end date is null or the end date is greater than the
1054: -- termination date.
1055: --
1056: -- Fix for bug 4147802 starts here. used fnd_user_resp_groups_direct view
1057: -- in place of fnd_user_resp_groups. Also the column description is removed.
1058: --
1059: CURSOR lc_get_user_resp (c_user_id in number)
1060: IS
1061: /*
1064: ,security_group_id
1065: ,start_date
1066: ,end_date
1067: -- ,description
1068: FROM fnd_user_resp_groups_direct
1069: WHERE user_id = c_user_id
1070: AND nvl(end_date, l_date + 1) > l_date
1071: AND trunc(sysdate) between start_date and nvl(end_date,sysdate); --5090502
1072: */
1075: ,furgd.security_group_id
1076: ,furgd.start_date
1077: ,furgd.end_date
1078: -- ,description
1079: FROM fnd_user_resp_groups_direct furgd, FND_RESPONSIBILITY fr
1080: WHERE furgd.user_id = c_user_id
1081: AND fr.responsibility_id = furgd.responsibility_id
1082: AND trunc(sysdate) between fr.start_date and nvl(fr.end_date,sysdate)
1083: AND nvl(furgd.end_date, l_date + 1) > l_date
1129: --
1130: hr_utility.set_location(l_proc, 20);
1131: --
1132: --
1133: -- Update fnd_user.end_date with the p_inactivate_date passed in
1134: -- A person may have more than 1 user accounts opened. Need to
1135: -- get all the user ids associated to the person.
1136: --
1137: FOR get_user_ids in lc_get_user_id
1139: --
1140: ----------------------------------------------------------------------------
1141: -- NOTE:
1142: -- As of the time writing this code, the allowable update function is to
1143: -- inactivate an fnd_user.date_to when an employee is terminated.
1144: -- No code is provided to massively update other attributes of the fnd_user
1145: -- rec, such as the password. For bulk changes to password, we need to know
1146: -- the old password (decrypted) and as of now, there is no way to decrypt
1147: -- a password without using the java code. Hence, the only functionality
1140: ----------------------------------------------------------------------------
1141: -- NOTE:
1142: -- As of the time writing this code, the allowable update function is to
1143: -- inactivate an fnd_user.date_to when an employee is terminated.
1144: -- No code is provided to massively update other attributes of the fnd_user
1145: -- rec, such as the password. For bulk changes to password, we need to know
1146: -- the old password (decrypted) and as of now, there is no way to decrypt
1147: -- a password without using the java code. Hence, the only functionality
1148: -- allowed for updating an fnd_user rec is to end date the record.
1144: -- No code is provided to massively update other attributes of the fnd_user
1145: -- rec, such as the password. For bulk changes to password, we need to know
1146: -- the old password (decrypted) and as of now, there is no way to decrypt
1147: -- a password without using the java code. Hence, the only functionality
1148: -- allowed for updating an fnd_user rec is to end date the record.
1149: ----------------------------------------------------------------------------
1150: hr_user_acct_internal.update_fnd_user
1151: (p_user_id => get_user_ids.user_id
1152: ,p_end_date => l_date
1146: -- the old password (decrypted) and as of now, there is no way to decrypt
1147: -- a password without using the java code. Hence, the only functionality
1148: -- allowed for updating an fnd_user rec is to end date the record.
1149: ----------------------------------------------------------------------------
1150: hr_user_acct_internal.update_fnd_user
1151: (p_user_id => get_user_ids.user_id
1152: ,p_end_date => l_date
1153: );
1154: --
1154: --
1155: -- Need to end date all rows in per_sec_profile_assignments associated
1156: -- the user id.
1157: -- The per_asp_upd(peasprhi.pkb) api will transparently end date the
1158: -- fnd_user_resp_groups records as well.
1159:
1160:
1161: FOR get_sec_prf_asg in lc_get_sec_profile_asg
1162: (c_user_id => get_user_ids.user_id)
1171: );
1172: END LOOP;
1173:
1174:
1175: -- Need to end date the fnd_user_resp_groups record for
1176: -- each user id.
1177: -- The cursor needs to return the application_id, start_date
1178: -- end_date, description, responsibility_id in addition to
1179: -- user_id because these attributes are the required parameters
1176: -- each user id.
1177: -- The cursor needs to return the application_id, start_date
1178: -- end_date, description, responsibility_id in addition to
1179: -- user_id because these attributes are the required parameters
1180: -- in fnd_user_resp_groups update_row.
1181: --
1182: -- If 'ENABLE_SECURITY_GROUPS' = 'Y' and the data are setup
1183: -- correctly, there should not be any rows returned from the
1184: -- lc_get_user_resp cursor because the peasprhi.pkb api would
1181: --
1182: -- If 'ENABLE_SECURITY_GROUPS' = 'Y' and the data are setup
1183: -- correctly, there should not be any rows returned from the
1184: -- lc_get_user_resp cursor because the peasprhi.pkb api would
1185: -- have already end dated the fnd_user_resp_groups record. If
1186: -- we have rows returned from the lc_get_user_resp, that means
1187: -- 'ENABLE_SECURITY_GROUPS' = 'N'. Hence, we need to end date
1188: -- the fnd_user_resp_groups rows.
1189: FOR get_user_resp in lc_get_user_resp
1184: -- lc_get_user_resp cursor because the peasprhi.pkb api would
1185: -- have already end dated the fnd_user_resp_groups record. If
1186: -- we have rows returned from the lc_get_user_resp, that means
1187: -- 'ENABLE_SECURITY_GROUPS' = 'N'. Hence, we need to end date
1188: -- the fnd_user_resp_groups rows.
1189: FOR get_user_resp in lc_get_user_resp
1190: (c_user_id => get_user_ids.user_id)
1191: LOOP
1192: hr_utility.trace('Calling update_fnd_user_resp_groups with ');
1188: -- the fnd_user_resp_groups rows.
1189: FOR get_user_resp in lc_get_user_resp
1190: (c_user_id => get_user_ids.user_id)
1191: LOOP
1192: hr_utility.trace('Calling update_fnd_user_resp_groups with ');
1193: hr_utility.trace('user_id' || get_user_ids.user_id);
1194: hr_utility.trace('security_group_id' || get_user_resp.security_group_id);
1195: hr_utility.trace('p_end_date' || l_date);
1196:
1193: hr_utility.trace('user_id' || get_user_ids.user_id);
1194: hr_utility.trace('security_group_id' || get_user_resp.security_group_id);
1195: hr_utility.trace('p_end_date' || l_date);
1196:
1197: hr_user_acct_internal.update_fnd_user_resp_groups
1198: (p_user_id => get_user_ids.user_id
1199: ,p_responsibility_id => get_user_resp.responsibility_id
1200: ,p_resp_application_id
1201: => get_user_resp.responsibility_application_id