Search Results per_respowner_util_ss




Overview
Explore in AI Chat

Overview

APPS.PER_RESPOWNER_UTIL_SS is a PL/SQL utility package in the Oracle E-Business Suite Applications schema (APPS) that supports the Responsibility Owner feature introduced in EBS 12.1.1 and carried forward into 12.2.2. Responsibility ownership allows an administrator to designate a specific user as the "owner" of a responsibility; that owner can then delegate or approve access to the responsibility through the Oracle Approvals Management / User Management infrastructure, rather than requiring a System Administrator to grant every assignment manually. The "_SS" suffix indicates that this is a seed/support package, typically consumed internally by Oracle's own forms, workflows, and concurrent programs rather than being documented as a public API.

The package's central role is to maintain the staging (temporary) table used during ownership validation and delegation processing, and to raise the workflow events that notify the Workflow Business Events System (WF_BES) when ownership is granted or revoked. In the ETRM metadata it is classified under API classification OTHER, has four documented subprograms, and references the PER_RESPONSIBILITY_OWNER entity alongside several FND and workflow tables. It is not itself referenced by any other package, confirming its status as a leaf-level utility invoked directly by forms or workflow subscribers.

Key Procedures and Functions

  • POPULATE_RESPOWNER_TEMP_TABLE — Populates the temporary/staging table that holds responsibility-owner records for a given processing run. This is the entry point that gathers the relevant owner rows so that subsequent validation or workflow logic can operate on a consistent snapshot.
  • RAISE_WFEVENT — Raises a Workflow event through the Business Events System. It consumes a parameter list (WF_PARAMETER_LIST_T) so that event payload attributes can be passed to subscribers, enabling downstream workflow processes to react to ownership changes.
  • REVOKE_BLOCK — Handles the revocation logic that prevents or blocks further access to a responsibility once ownership has been withdrawn. It enforces the business rule that a revoked owner can no longer delegate or approve access.
  • REVOKE_ACCESS_WFEVENT_SUBSCRB — The workflow event subscription handler invoked when a revoke-access event is raised. It is the callback that a workflow process calls to complete the revocation, tying the package into the Workflow subscription model.

Tables Accessed

The package reads and writes a small, focused set of objects. PER_RESPONSIBILITY_OWNER is the primary entity table storing which user owns which responsibility. FND_GRANTS and FND_OBJECTS are accessed to reconcile actual grants and object definitions during revoke processing. FND_RESPONSIBILITY and FND_USER provide the responsibility and user definitions required to resolve owner identities. HR_API_TRANSACTIONS_S is referenced, indicating interaction with the HR API transaction tracking used when owner records are maintained through the HR security model. WF_PARAMETER_LIST_T supplies the workflow event parameter list used by RAISE_WFEVENT, while DUAL and PLITBLM support internal PL/SQL utility operations. Access to these objects is made through APPS synonyms, with the underlying definitions owned by SYS or the respective product schemas.

Usage Notes

PER_RESPOWNER_UTIL_SS is not a public API and should not be called directly from custom code unless Oracle's own documentation for the responsibility-owner feature explicitly requires it. It is typically invoked in three contexts: from the Users and Responsibilities forms during owner assignment and revocation; from concurrent programs that process ownership delegations in batch; and from workflow event subscriptions where REVOKE_ACCESS_WFEVENT_SUBSCRB acts as the handler. Because the package belongs to the APPS schema and is marked VALID, its execution is subject to standard APPS schema privileges. Customizations that need to inspect or act on ownership data should query PER_RESPONSIBILITY_OWNER directly or subscribe to the same workflow events rather than invoking these procedures, since the "_SS" designation signals that the signatures and behavior are reserved for Oracle internal use and may change between releases without notice.