Search Results fnd_resp




Overview
Explore in AI Chat

Overview

APPS.WF_FND_RESP_ROLES_VL is a read-only Oracle E-Business Suite view that exposes Oracle FND responsibilities in a role-oriented form suitable for consumption by Oracle Workflow and related role-resolution mechanisms. The name encodes its purpose: WF denotes the Workflow schema context, FND_RESP identifies the FND responsibility entity, and the ROLE suffix indicates that each row is published as a workflow role. The view is owned by APPS, the canonical repository for EBS-visible objects, and is available in both Release 12.1.1 and 12.2.2. Because responsibilities are the principal authorization construct in EBS, this view provides the bridge that allows notification routing, approval hierarchies, and workflow participant lists to reference responsibilities by a synthetic role key rather than by raw application and responsibility identifiers.

Underlying Base Objects

The view is defined exclusively over two documented base objects, both referenced as synonyms in the EBS data dictionary:

Internally, FND_RESPONSIBILITY_TL resolves to the base FND_RESPONSIBILITY table joined to FND_RESPONSIBILITY_TL for translatable columns. The view applies no aggregation and no filtering beyond the language restriction, so it is functionally a projection and key-derivation layer over the responsibility definition. It is distinct from FND_RESPONSIBILITY_VL, which exposes the same underlying data with a different key scheme; WF_FND_RESP_ROLES_VL exists specifically to satisfy Workflow role naming conventions.

Key Columns

The view projects six columns. Two are generated expressions and four are direct table columns:

  • Role key (unnamed first column) — the concatenated expression 'FND_RESP'||APPLICATION_ID||':'||RESPONSIBILITY_ID, producing values such as FND_RESP660:20420. This is the Workflow role identifier consumed by role-lookup APIs.
  • RESPONSIBILITY_NAME — the responsibility name in the current language.
  • DESCRIPTION — the responsibility description, also language-dependent.
  • LANGUAGE — the language code of the returned name and description.
  • SOURCE_LANG — the source language of the translated record, used for translation tracking.
  • Application role key — the concatenated expression 'FND_RESP'||APPLICATION_ID, a coarser role key that groups all responsibilities of an application.
  • RESPONSIBILITY_ID — the numeric primary key of the responsibility, retained for joins back to FND_RESPONSIBILITY.

Common Use Cases and Queries

The view is typically queried to resolve a responsibility to its Workflow role key, to enumerate available roles for a notification or approval configuration, or to report on responsibility definitions with their role naming. A representative query resolves a specific responsibility:

  • SELECT * FROM APPS.WF_FND_RESP_ROLES_VL WHERE RESPONSIBILITY_ID = 20420;
  • SELECT RESPONSIBILITY_NAME FROM APPS.WF_FND_RESP_ROLES_VL WHERE 'FND_RESP'||APPLICATION_ID||':'||RESPONSIBILITY_ID = :p_role;
  • SELECT RESPONSIBILITY_ID, RESPONSIBILITY_NAME, LANGUAGE FROM APPS.WF_FND_RESP_ROLES_VL WHERE APPLICATION_ID = 660 ORDER BY RESPONSIBILITY_NAME;

In integration scenarios, the derived role keys are passed to Workflow APIs such as WF_ROLE APIs. Cross-application reporting commonly joins this view to FND_APPLICATION_VL to translate APPLICATION_ID into an application name. Because the view is not secured by responsibility-based row filtering, access should be governed through the calling application or a secured synonym, and queries should be bounded by application or responsibility predicates to avoid scanning the full translated responsibility set.