Results for “fnd_responsibility_vl”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

FND_RESPONSIBILITY_VL is a validation (VL) view owned by the APPS schema in Oracle E-Business Suite. It presents responsibility definition data by joining the base transactional table FND_RESPONSIBILITY with its translation table FND_RESPONSIBILITY_TL, exposing the responsibility name and description in the session's current language. The "_VL" suffix denotes a view that combines a language-independent ("_B") entity with its translated ("_TL") attributes, and it is the standard interface used by Oracle's own forms, concurrent programs, and reporting layers wherever a responsibility must be resolved to a user-readable name.

In Oracle EBS 12.1.1 and 12.2.2 the object is identified as a VIEW in the APPS schema with VALID status under the FND — Application Object Library product. Because it resolves the translation automatically via USERENV('LANG'), it functions as the canonical reporting and integration entry point for responsibility metadata, sparing callers from writing their own language-join logic.

Underlying Base Objects

The ETRM metadata documents two referenced base objects, both catalogued as synonyms in APPS:

• FND_RESPONSIBILITY — the language-independent definition table holding the responsibility identifier, key, application, menu, data group, request group, effective dates, and standard WHO audit columns. Referenced in the view text by alias B.
• FND_RESPONSIBILITY_TL — the translation table supplying RESPONSIBILITY_NAME and DESCRIPTION for each installed language. Referenced by alias T.

The join is performed on RESPONSIBILITY_ID and APPLICATION_ID in both directions, and is further constrained by T.LANGUAGE = USERENV('LANG'), ensuring exactly one translated row is returned per responsibility for the current session language.

Key Columns

• ROW_ID — the ROWID of the FND_RESPONSIBILITY row; useful for direct row identification and some forms-based lookups.
• APPLICATION_ID / RESPONSIBILITY_ID — the composite key uniquely identifying a responsibility; both are required for correct joins to FND_RESPONSIBILITY_TL and related assignment tables.
• RESPONSIBILITY_KEY — the developer-facing short name (e.g., SYSTEM_ADMINISTRATOR) used in FND_RESPONSIBILITY assignments and code.
• RESPONSIBILITY_NAME / DESCRIPTION — translated, user-visible attributes sourced from FND_RESPONSIBILITY_TL and therefore language-sensitive.
• MENU_ID, DATA_GROUP_ID, DATA_GROUP_APPLICATION_ID, REQUEST_GROUP_ID, GROUP_APPLICATION_ID — pointers to the menu, data group, and request group that define the responsibility's functional and security behavior.
• START_DATE / END_DATE — effective dating controlling when the responsibility is active.
• WEB_HOST_NAME / WEB_AGENT_NAME — web-tier binding information used for self-service responsibilities.
• VERSION — the responsibility's definition version, used in certain validation routines.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard audit columns inherited from FND_RESPONSIBILITY.

Common Use Cases and Queries

Typical scenarios include resolving responsibility identifiers to display names in custom reports, validating responsibility assignments, and extracting responsibility metadata for integrations or upgrades.

• Listing all responsibilities with their translated names:
  SELECT responsibility_id, application_id, responsibility_key, responsibility_name FROM apps.fnd_responsibility_vl ORDER BY responsibility_name;
• Looking up a responsibility by key:
  SELECT responsibility_id, responsibility_name FROM apps.fnd_responsibility_vl WHERE responsibility_key = 'SYSTEM_ADMINISTRATOR';
• Joining to user assignments to report which users hold which responsibility:
  SELECT u.user_name, r.responsibility_name FROM fnd_user u, fnd_user_resp_groups ur, apps.fnd_responsibility_vl r WHERE u.user_id = ur.user_id AND ur.responsibility_id = r.responsibility_id AND ur.responsibility_application_id = r.application_id;
• Filtering by effective dates to identify currently active responsibilities:
  SELECT responsibility_id, responsibility_name FROM apps.fnd_responsibility_vl WHERE SYSDATE BETWEEN start_date AND NVL(end_date, SYSDATE);

Because the view enforces the language join internally, it is preferred over querying FND_RESPONSIBILITY directly whenever the translated name is required.