eTRM uses javascript that opens and focuses a separate window to display reports. Your browser does not appear to support javascript. This should not prevent you from using eTRM but it does mean the window focus feature will not work. Please check the contents of other windows on your desktop if you click on a link that does not appear to do anything.

APPS.HR_USER_ACCT_UTILITY dependencies on FND_USER

Line 60: -- RECORD STRUCTURE FOR FND_USERS

56: -- program is intended for HR Application use only.
57: -------------------------------------------------------------------------------
58: --
59: --
60: -- RECORD STRUCTURE FOR FND_USERS
61: -- ==============================
62: TYPE fnd_user_rec IS RECORD
63: (user_name fnd_user.user_name%type
64: ,password varchar2(30)

Line 62: TYPE fnd_user_rec IS RECORD

58: --
59: --
60: -- RECORD STRUCTURE FOR FND_USERS
61: -- ==============================
62: TYPE fnd_user_rec IS RECORD
63: (user_name fnd_user.user_name%type
64: ,password varchar2(30)
65: ,start_date fnd_user.start_date%type
66: ,end_date fnd_user.end_date%type

Line 63: (user_name fnd_user.user_name%type

59: --
60: -- RECORD STRUCTURE FOR FND_USERS
61: -- ==============================
62: TYPE fnd_user_rec IS RECORD
63: (user_name fnd_user.user_name%type
64: ,password varchar2(30)
65: ,start_date fnd_user.start_date%type
66: ,end_date fnd_user.end_date%type
67: ,email_address fnd_user.email_address%type

Line 65: ,start_date fnd_user.start_date%type

61: -- ==============================
62: TYPE fnd_user_rec IS RECORD
63: (user_name fnd_user.user_name%type
64: ,password varchar2(30)
65: ,start_date fnd_user.start_date%type
66: ,end_date fnd_user.end_date%type
67: ,email_address fnd_user.email_address%type
68: ,fax fnd_user.fax%type
69: ,description fnd_user.description%type

Line 66: ,end_date fnd_user.end_date%type

62: TYPE fnd_user_rec IS RECORD
63: (user_name fnd_user.user_name%type
64: ,password varchar2(30)
65: ,start_date fnd_user.start_date%type
66: ,end_date fnd_user.end_date%type
67: ,email_address fnd_user.email_address%type
68: ,fax fnd_user.fax%type
69: ,description fnd_user.description%type
70: ,password_date fnd_user.password_date%type

Line 67: ,email_address fnd_user.email_address%type

63: (user_name fnd_user.user_name%type
64: ,password varchar2(30)
65: ,start_date fnd_user.start_date%type
66: ,end_date fnd_user.end_date%type
67: ,email_address fnd_user.email_address%type
68: ,fax fnd_user.fax%type
69: ,description fnd_user.description%type
70: ,password_date fnd_user.password_date%type
71: ,language fnd_profile_option_values.profile_option_value%type

Line 68: ,fax fnd_user.fax%type

64: ,password varchar2(30)
65: ,start_date fnd_user.start_date%type
66: ,end_date fnd_user.end_date%type
67: ,email_address fnd_user.email_address%type
68: ,fax fnd_user.fax%type
69: ,description fnd_user.description%type
70: ,password_date fnd_user.password_date%type
71: ,language fnd_profile_option_values.profile_option_value%type
72: ,host_port varchar2(2000)

Line 69: ,description fnd_user.description%type

65: ,start_date fnd_user.start_date%type
66: ,end_date fnd_user.end_date%type
67: ,email_address fnd_user.email_address%type
68: ,fax fnd_user.fax%type
69: ,description fnd_user.description%type
70: ,password_date fnd_user.password_date%type
71: ,language fnd_profile_option_values.profile_option_value%type
72: ,host_port varchar2(2000)
73: ,employee_id fnd_user.employee_id%type

Line 70: ,password_date fnd_user.password_date%type

66: ,end_date fnd_user.end_date%type
67: ,email_address fnd_user.email_address%type
68: ,fax fnd_user.fax%type
69: ,description fnd_user.description%type
70: ,password_date fnd_user.password_date%type
71: ,language fnd_profile_option_values.profile_option_value%type
72: ,host_port varchar2(2000)
73: ,employee_id fnd_user.employee_id%type
74: ,customer_id fnd_user.customer_id%type

Line 73: ,employee_id fnd_user.employee_id%type

69: ,description fnd_user.description%type
70: ,password_date fnd_user.password_date%type
71: ,language fnd_profile_option_values.profile_option_value%type
72: ,host_port varchar2(2000)
73: ,employee_id fnd_user.employee_id%type
74: ,customer_id fnd_user.customer_id%type
75: ,supplier_id fnd_user.supplier_id%type
76: );
77: --

Line 74: ,customer_id fnd_user.customer_id%type

70: ,password_date fnd_user.password_date%type
71: ,language fnd_profile_option_values.profile_option_value%type
72: ,host_port varchar2(2000)
73: ,employee_id fnd_user.employee_id%type
74: ,customer_id fnd_user.customer_id%type
75: ,supplier_id fnd_user.supplier_id%type
76: );
77: --
78: g_fnd_user_rec fnd_user_rec;

Line 75: ,supplier_id fnd_user.supplier_id%type

71: ,language fnd_profile_option_values.profile_option_value%type
72: ,host_port varchar2(2000)
73: ,employee_id fnd_user.employee_id%type
74: ,customer_id fnd_user.customer_id%type
75: ,supplier_id fnd_user.supplier_id%type
76: );
77: --
78: g_fnd_user_rec fnd_user_rec;
79: --

Line 78: g_fnd_user_rec fnd_user_rec;

74: ,customer_id fnd_user.customer_id%type
75: ,supplier_id fnd_user.supplier_id%type
76: );
77: --
78: g_fnd_user_rec fnd_user_rec;
79: --
80: -- ----------------------------------------------------------------------------
81: -- NOTE: Since new responsibility can use a template responsibility's
82: -- values, we need to use API constant system defaults to differentiate

Line 101: -- For R11i, fnd_user_responsibility is replaced with fnd_user_resp_groups.

97: -- USAGE NOTES FOR CREATING/UPDATING A RESPONSIBILTY, ASSOCIATING A
98: -- RESPONSIBILITY, SECURITY GROUP TO A USERNAME:
99: --
100: -- ***************************************************************************
101: -- For R11i, fnd_user_responsibility is replaced with fnd_user_resp_groups.
102: -- If the profile option 'ENABLE_SECURITY_GROUPS' for the Application is 'Y',
103: -- then you'll need to populate the sec_group_id, sec_profile_id fields at the
104: -- end of this record structure. The system will insert a row into
105: -- per_sec_profile_assignments as well as to fnd_user_resp_groups.

Line 105: -- per_sec_profile_assignments as well as to fnd_user_resp_groups.

101: -- For R11i, fnd_user_responsibility is replaced with fnd_user_resp_groups.
102: -- If the profile option 'ENABLE_SECURITY_GROUPS' for the Application is 'Y',
103: -- then you'll need to populate the sec_group_id, sec_profile_id fields at the
104: -- end of this record structure. The system will insert a row into
105: -- per_sec_profile_assignments as well as to fnd_user_resp_groups.
106: --
107: -- If the profile option 'ENABLE_SECURITY_GROUPS' for the Application is 'N',
108: -- that means you remain to use the R11 way of responsibility and security profile
109: -- set up. There is no need to fill in the values of sec_group_id and

Line 110: -- sec_profile_id fields. The system will insert a row into fnd_user_resp_groups

106: --
107: -- If the profile option 'ENABLE_SECURITY_GROUPS' for the Application is 'N',
108: -- that means you remain to use the R11 way of responsibility and security profile
109: -- set up. There is no need to fill in the values of sec_group_id and
110: -- sec_profile_id fields. The system will insert a row into fnd_user_resp_groups
111: -- only.
112: -- ***************************************************************************
113: --
114: -- existing_resp_id - optional. If creating a new responsibility and would

Line 237: -- fnd_user_resp_groups.start_date.

233: --
234: -- user_resp_start_date - mandatory for associating the above responsibility to
235: -- the new user. It should be in date data type.
236: -- Length cannot exceed the length of
237: -- fnd_user_resp_groups.start_date.
238: -- Do not fill in this field with a hr_api.g_date
239: -- because each user should have his/her own start_date.
240: --
241: -- user_resp_end_date - optional for associating the above responsibility to

Line 245: -- fnd_user_resp_groups.end_date.

241: -- user_resp_end_date - optional for associating the above responsibility to
242: -- the new user. It should be in date data type and must be
243: -- larger than or equal to user_resp_start_date.
244: -- Length can not exceed the length of
245: -- fnd_user_resp_groups.end_date.
246: -- Do not fill in this field with a hr_api.g_date
247: -- because each user should have his/her own end_date.
248: -- If no end_date is aniticpated, set this field to null.
249: --

Line 252: -- fnd_user_resp_groups.description.

248: -- If no end_date is aniticpated, set this field to null.
249: --
250: -- user_resp_description - optional for associating the responsibility to the
251: -- new user. Length cannot exceed the length of
252: -- fnd_user_resp_groups.description.
253: -- Do not fill in this field with a hr_api.g_varchar2
254: -- because each user should have his/her own description.
255: --
256: -- **** The following two fields sec_group_id and sec_profile_id

Line 266: -- **** fnd_user_resp_groups will be populated but not

262: -- **** and new_resp_key is NOT null) to the new user using the sec_group_id
263: -- **** and the sec_profile_id entered. However, you have an option to leave
264: -- **** these two fields to null if you want to use the view-all security
265: -- **** profile of the employee's business group. In this case, only
266: -- **** fnd_user_resp_groups will be populated but not
267: -- **** per_security_profile_assignment.
268: -- **** If 'ENABLE_SECURITY_GROUPS' = 'N', ignore these two fields.
269: --
270: -- sec_group_id - optional for 'ENABLE_SECURITY_GROUPS' profile option =

Line 281: -- be inserted into fnd_user_resp_groups table.

277: -- id. If this field is null or sec_profile_id is null,
278: -- then the view-all security profile for the employee's
279: -- business group will be used. No row will be inserted
280: -- into per_security_profile_assignments. Only 1 row will
281: -- be inserted into fnd_user_resp_groups table.
282: -- If 'ENABLE_SECURITY_GROUPS' profile option = 'N', leave
283: -- this field null.
284: --
285: -- sec_profile_id - optional for 'ENABLE_SECURITY_GROUPS' profile option

Line 296: -- be inserted into fnd_user_resp_groups table.

292: -- id. If this field is null or sec_profile_id is null,
293: -- then the view-all security profile for the employee's
294: -- business group will be used. No row will be inserted
295: -- into per_security_profile_assignments. Only 1 row will
296: -- be inserted into fnd_user_resp_groups table.
297: -- If 'ENABLE_SECURITY_GROUPS' profile option = 'N', leave
298: -- this field null.
299: --
300: -------------------------------------------------------------------------------

Line 324: ,user_resp_start_date fnd_user_resp_groups.start_date%type

320: ,new_resp_req_grp_app_id fnd_application.application_id%type
321: ,new_resp_version fnd_responsibility.version%type
322: ,new_resp_web_host_name fnd_responsibility.web_host_name%type
323: ,new_resp_web_agent_name fnd_responsibility.web_agent_name%type
324: ,user_resp_start_date fnd_user_resp_groups.start_date%type
325: ,user_resp_end_date fnd_user_resp_groups.end_date%type
326: ,user_resp_description fnd_user_resp_groups.description%type
327: ,sec_group_id
328: per_sec_profile_assignments.security_group_id%type

Line 325: ,user_resp_end_date fnd_user_resp_groups.end_date%type

321: ,new_resp_version fnd_responsibility.version%type
322: ,new_resp_web_host_name fnd_responsibility.web_host_name%type
323: ,new_resp_web_agent_name fnd_responsibility.web_agent_name%type
324: ,user_resp_start_date fnd_user_resp_groups.start_date%type
325: ,user_resp_end_date fnd_user_resp_groups.end_date%type
326: ,user_resp_description fnd_user_resp_groups.description%type
327: ,sec_group_id
328: per_sec_profile_assignments.security_group_id%type
329: ,sec_profile_id per_sec_profile_assignments.security_profile_id%type

Line 326: ,user_resp_description fnd_user_resp_groups.description%type

322: ,new_resp_web_host_name fnd_responsibility.web_host_name%type
323: ,new_resp_web_agent_name fnd_responsibility.web_agent_name%type
324: ,user_resp_start_date fnd_user_resp_groups.start_date%type
325: ,user_resp_end_date fnd_user_resp_groups.end_date%type
326: ,user_resp_description fnd_user_resp_groups.description%type
327: ,sec_group_id
328: per_sec_profile_assignments.security_group_id%type
329: ,sec_profile_id per_sec_profile_assignments.security_profile_id%type
330: );

Line 530: -- - fnd_user.user_id if profile_level_name = "USER".

526: -- at the new responsibility level or at the new user level.
527: -- It must be one of the following values:
528: -- - fnd_responsibility.responsbility_key if
529: -- profile_level_name = "RESP"
530: -- - fnd_user.user_id if profile_level_name = "USER".
531: --
532: -- Examples:
533: -- - to create a new profile option value for the
534: -- responsibility "US HRMS Manager", this field will be the

Line 539: -- "SYSADMIN", this field will be the fnd_user.user_id, which

535: -- fnd_responsibility.responsibility_key, which is
536: -- "US_HRMS_MANAGER". If the responsibility is new, use
537: -- the fnd_responsibility_tbl.new_resp_key value.
538: -- - to create a new profile option value for the user
539: -- "SYSADMIN", this field will be the fnd_user.user_id, which
540: -- is 0.
541: --
542: -- profile_level_value_app_id - mandatory for creating a new profile option
543: -- value at the new responsibility level. If profile_level_name