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.BEN_PROCESS_USER_SS_API dependencies on PER_SEC_PROFILE_ASSIGNMENTS

Line 168: ,p_resp_app_id in per_sec_profile_assignments.responsibility_application_id%type

164: (p_user_id in fnd_user.user_id%type
165: ,p_sec_group_id in fnd_security_groups.security_group_id%type
166: ,p_sec_profile_id in per_security_profiles.security_profile_id%type
167: ,p_resp_id in fnd_responsibility.responsibility_id%type
168: ,p_resp_app_id in per_sec_profile_assignments.responsibility_application_id%type
169: ,p_start_date in per_sec_profile_assignments.start_date%type
170: ,p_end_date in per_sec_profile_assignments.end_date%type default null
171: ,p_business_group_id in per_sec_profile_assignments.business_group_id%type default null
172:

Line 169: ,p_start_date in per_sec_profile_assignments.start_date%type

165: ,p_sec_group_id in fnd_security_groups.security_group_id%type
166: ,p_sec_profile_id in per_security_profiles.security_profile_id%type
167: ,p_resp_id in fnd_responsibility.responsibility_id%type
168: ,p_resp_app_id in per_sec_profile_assignments.responsibility_application_id%type
169: ,p_start_date in per_sec_profile_assignments.start_date%type
170: ,p_end_date in per_sec_profile_assignments.end_date%type default null
171: ,p_business_group_id in per_sec_profile_assignments.business_group_id%type default null
172:
173: ) is

Line 170: ,p_end_date in per_sec_profile_assignments.end_date%type default null

166: ,p_sec_profile_id in per_security_profiles.security_profile_id%type
167: ,p_resp_id in fnd_responsibility.responsibility_id%type
168: ,p_resp_app_id in per_sec_profile_assignments.responsibility_application_id%type
169: ,p_start_date in per_sec_profile_assignments.start_date%type
170: ,p_end_date in per_sec_profile_assignments.end_date%type default null
171: ,p_business_group_id in per_sec_profile_assignments.business_group_id%type default null
172:
173: ) is
174: --

Line 171: ,p_business_group_id in per_sec_profile_assignments.business_group_id%type default null

167: ,p_resp_id in fnd_responsibility.responsibility_id%type
168: ,p_resp_app_id in per_sec_profile_assignments.responsibility_application_id%type
169: ,p_start_date in per_sec_profile_assignments.start_date%type
170: ,p_end_date in per_sec_profile_assignments.end_date%type default null
171: ,p_business_group_id in per_sec_profile_assignments.business_group_id%type default null
172:
173: ) is
174: --
175: --

Line 190: per_sec_profile_assignments.sec_profile_assignment_id%type := null;

186: --
187: l_bg_id per_security_profiles.business_group_id%type := null;
188: l_dummy number default null;
189: l_sec_prof_asg_id
190: per_sec_profile_assignments.sec_profile_assignment_id%type := null;
191: l_obj_vers_num
192: per_sec_profile_assignments.object_version_number%type := null;
193: l_proc varchar2(72) := g_package|| 'create_sec_profile_asg';
194:

Line 192: per_sec_profile_assignments.object_version_number%type := null;

188: l_dummy number default null;
189: l_sec_prof_asg_id
190: per_sec_profile_assignments.sec_profile_assignment_id%type := null;
191: l_obj_vers_num
192: per_sec_profile_assignments.object_version_number%type := null;
193: l_proc varchar2(72) := g_package|| 'create_sec_profile_asg';
194:
195: BEGIN
196: hr_utility.set_location('Entering:' || l_proc, 10);

Line 252: -- per_sec_profile_assignments as well as fnd_user_resp_groups.

248: end if;
249: end if;
250: --
251: -- Now call the per_asp_ins.ins which will insert a row into
252: -- per_sec_profile_assignments as well as fnd_user_resp_groups.
253: per_asp_ins.ins
254: (p_user_id => p_user_id
255: ,p_security_group_id => p_sec_group_id
256: ,p_business_group_id => l_bg_id

Line 625: -- insert one row into per_sec_profile_assignments as well as to

621: -- into fnd_user_resp_groups only if view-all security profile of the
622: -- employee's business group is to be used.
623: -- If a restricted security
624: -- profile is to be used, then we must call hrasprhi.pkb which will
625: -- insert one row into per_sec_profile_assignments as well as to
626: -- fnd_user_resp_groups.
627:
628: -- Insert into fnd_user_resp_groups only
629: -- get the security_group_id for the employee's business_group_id

Line 664: -- call peasprhi.pkb to insert into per_sec_profile_assignments

660: ' after create_fnd_user_resp_groups', 54);
661: --
662: else
663: -- sec_group_id and sec_profile_id are filled in
664: -- call peasprhi.pkb to insert into per_sec_profile_assignments
665: -- as well as fnd_user_resp_groups.
666:
667: hr_utility.set_location (l_proc ||
668: ' before create_sec_profile_asg', 56);

Line 670: -- Insert this row into per_sec_profile_assignments

666:
667: hr_utility.set_location (l_proc ||
668: ' before create_sec_profile_asg', 56);
669:
670: -- Insert this row into per_sec_profile_assignments
671: create_sec_profile_asg
672: (p_user_id => l_user_id
673: ,p_sec_group_id => ben_process_user_utility.g_fnd_resp_record.security_group_id
674: ,p_sec_profile_id => ben_process_user_utility.g_fnd_resp_record.security_profile_id