[Home] [Help]
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
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
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
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;