DBA Data[Home] [Help]

APPS.BEN_PROCESS_USER_UTILITY dependencies on FND_USER

Line 56: --RECORD STRUCTURE FOR FND_USERS

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)

Line 58: TYPE fnd_user_record IS RECORD

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

Line 59: (user_name fnd_user.user_name%type

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

Line 61: ,start_date fnd_user.start_date%type

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

Line 62: ,end_date fnd_user.end_date%type

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

Line 63: ,last_logon_date fnd_user.last_logon_date%type

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

Line 64: ,password_date fnd_user.password_date%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

Line 65: ,password_accesses_left fnd_user.password_accesses_left%type

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

Line 66: ,password_lifespan_accesses fnd_user.password_lifespan_accesses%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

Line 67: ,password_lifespan_days fnd_user.password_lifespan_days%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

Line 68: ,email_address fnd_user.email_address%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

Line 69: ,fax fnd_user.fax%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

Line 70: ,description fnd_user.description%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: );

Line 71: ,employee_id fnd_user.employee_id%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: --

Line 72: ,customer_id fnd_user.customer_id%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;

Line 73: ,supplier_id fnd_user.supplier_id%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: --

Line 76: g_fnd_user_record fnd_user_record;

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

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

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

Line 92: -- sec_profile_id fields. The system will insert a row into 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

Line 112: -- be inserted into fnd_user_resp_groups table.

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

Line 125: -- be inserted into fnd_user_resp_groups table.

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: ----------------------------------------------------------------------------