Search Results sync_roles_all_resp_secgrps




Overview
Explore in AI Chat

Overview

APPS.FND_USER_RESP_GROUPS_API is the public table handler for the FND_USER_RESP_GROUPS table, the central repository of user-to-responsibility assignments in Oracle E-Business Suite. In release 12.1.1 and 12.2.2 this package is the supported programmatic interface for creating, updating, validating, and synchronizing responsibility assignments, replacing direct DML against the underlying table. Because responsibility assignments drive application and function security, data corruption in this area can expose secured functionality or lock users out of applications; the package therefore encapsulates the business rules that Forms-based maintenance and bulk loading utilities require. The package is declared AUTHID CURRENT_USER and is classified as a public API in the ETRM repository, carrying the display name "User Responsibility Group" and compatibility level S.

Key Procedures and Functions

Seventeen documented entry points are exposed, covering lookup, validation, maintenance, bulk loading, and role synchronization:

  • ASSIGNMENT_EXISTS — Determines whether a user/responsibility/security group assignment already exists. It deliberately ignores start and end dates on the user, the responsibility, and the assignment itself. Its direct_flag argument controls whether the check considers direct assignments only, indirect assignments sourced from WF_ROLE_HIERARCHY only, or either. The closely related ASSIGNMENT_CHECK provides the assignment-verification entry point that callers commonly search for when validating a prospective assignment.
  • VALIDATE_SECURITY_CONTEXT — Confirms that a given user may legitimately use a given responsibility. Unlike ASSIGNMENT_EXISTS, this routine observes start and end dates on the user, the responsibility, and the responsibility assignment.
  • ROLE_NAME_FROM_RESP / ROLE_NAME_FROM_RESP_NO_EXC — Derive the corresponding Oracle Workflow role name for a responsibility; the _NO_EXC variant suppresses exceptions during derivation, suited to bulk processing where a single failure should not abort the run.
  • LOCK_ASSIGNMENT / INSERT_ASSIGNMENT / UPDATE_ASSIGNMENT — The core maintenance primitives. LOCK_ASSIGNMENT acquires the row lock, INSERT_ASSIGNMENT creates a new assignment, and UPDATE_ASSIGNMENT modifies an existing one, together forming the transaction pattern required for concurrent-safe updates.
  • UPLOAD_ASSIGNMENT / LOAD_ROW — Support bulk upload and row-at-a-time loading, typically from loader programs or interface tables rather than interactive sessions.
  • SYNC_ROLES_ONE_RESP_SECGRP, SYNC_ROLES_ALL_SECGRPS, SYNC_ROLES_ALL_RESPS, SYNC_ROLES_ALL_RESP_SECGRPS, SYNC_ROLES_ALL_SECGRPS_INT — Replicate responsibility assignments into Oracle Workflow local roles so that role-based notification and workflow routing remain consistent with security configuration. The scope varies from a single responsibility/security-group pair to every responsibility and security group.
  • ONE_TIME_FURG_TO_WF_UPGRADE / UPGRADE_RESP_ROLE — Migration utilities used to move existing FND_USER_RESP_GROUPS assignments into the Workflow role model, including the one-time conversion upgrade.

Tables Accessed

The package reads FND_USER, FND_RESPONSIBILITY, FND_RESPONSIBILITY_TL, FND_APPLICATION, FND_SECURITY_GROUPS, FND_SECURITY_GROUPS_TL, and FND_LANGUAGES to resolve and validate assignment attributes and translated names. It writes FND_USER_RESP_GROUPS as its primary target, and it interacts with WF_LOCAL_ROLES and WF_PARAMETER_LIST_T to create and synchronize Workflow roles. DUAL supports internal single-row queries. All references are made through APPS synonyms.

Usage Notes

The package is invoked from the Users form and responsibility maintenance forms, from concurrent programs that load or refresh assignments, and from the role synchronization and upgrade routines that run after patching or migration. Custom code should call these APIs rather than issuing DML against FND_USER_RESP_GROUPS, and should follow the lock/insert/update sequence to avoid concurrency errors. With twenty-eight dependent packages, changes to this API surface affect a broad set of EBS components, so callers should rely only on documented entry points.