APPS.HR_SIGNON dependencies on PER_BUSINESS_GROUPS

Line 45: -- The business group is derived by querying PER_BUSINESS_GROUPS

41: -- two ways:
42: --
43: -- ENABLE_SECURITY_GROUPS = 'Y'
44: -- Multi security groups can be used for the same responsibility.
45: -- The business group is derived by querying PER_BUSINESS_GROUPS
46: -- with the security group that the user selected at signon.
47: --
48: -- ENABLE_SECURITY_GROUPS = 'N'
49: -- Single security group model is in use, so the business group

Line 75: FROM per_business_groups

71: --
72: BEGIN
73: SELECT business_group_id
74: INTO l_business_group_id
75: FROM per_business_groups
76: WHERE security_group_id = to_char(p_security_group_id);
77: EXCEPTION
78: WHEN no_data_found THEN
79: l_business_group_id := NULL;

Line 128: FROM per_business_groups

124: --
125: CURSOR c_chk_bg_locked (l_business_group_id IN NUMBER)
126: IS
127: SELECT 'Y'
128: FROM per_business_groups
129: WHERE security_group_id = to_char(p_security_group_id)
130: AND business_group_id = l_business_group_id;
131: --
132: l_bg_lockout NUMBER DEFAULT NULL;

Line 336: -- per_business_groups view for any business groups (other than the

332: -- This is done by primarily checking the profile
333: -- ENABLE_SECURITY_GROUPS. If this is set then an additional check
334: -- is made to ensure that the enable security groups concurrent
335: -- program has been run - this is done by querying the
336: -- per_business_groups view for any business groups (other than the
337: -- setup business group) with a security_group_id of 0.
338: -- Note: any business groups created whilst security groups are not
339: -- enabled have a default value of 0.
340: --

Line 350: FROM per_business_groups

346: --
347: CURSOR c_check_sec_process_run
348: IS
349: SELECT 'Y'
350: FROM per_business_groups
351: WHERE business_group_id <> 0
352: AND security_group_id = '0';
353: --
354: BEGIN