APPS.FND_SECURITY_GROUPS_PKG dependencies on FND_USER_RESP_GROUPS_API

Line 224: fnd_user_resp_groups_api.sync_roles_all_resps(X_SECURITY_GROUP_ID,

220: -- is updated to resolve the problem where the Security group key
221: -- was being used in the display name for the role instead of the
222: -- security group name when the security group is initially created.
223:
224: fnd_user_resp_groups_api.sync_roles_all_resps(X_SECURITY_GROUP_ID,
225: X_SECURITY_GROUP_KEY);
226:
227: open c;
228: fetch c into X_ROWID;

Line 351: -- 'fnd_user_resp_groups_api.sync_roles_all_resps' from being called when

347: -- Bug3813798 Moved call so that the correct display name is
348: -- created for the roles defined for this security group.
349:
350: -- Bug 4943583. The following check prevents the expensive api
351: -- 'fnd_user_resp_groups_api.sync_roles_all_resps' from being called when
352: -- columns other than 'SECURITY_GROUP_NAME' (which is used in WF role
353: -- DISPLAY_NAME) are modified. This api needs to be called only when the
354: -- SECURITY_GROUP_NAME is modified.
355: -- This change is to improve the performance.

Line 367: fnd_user_resp_groups_api.sync_roles_all_resps(X_SECURITY_GROUP_ID,

363: if ((X_SECURITY_GROUP_KEY <> 'STANDARD') and
364: (X_SECURITY_GROUP_NAME <> p_security_group_name)) then
365: -- Call this api only if SECURITY_GROUP_KEY is not 'STANDARD'
366: -- and there is a change in SECURITY_GROUP_NAME
367: fnd_user_resp_groups_api.sync_roles_all_resps(X_SECURITY_GROUP_ID,
368: X_SECURITY_GROUP_KEY);
369: end if;
370: end if;
371: end UPDATE_ROW;