Results for “edr_sec_admin_vl”

4 results




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

Overview

EDR_SEC_ADMIN_VL is a multi-language (MLS) security administration view belonging to the EDR – E-Records product family in Oracle E-Business Suite. It exposes the administrative configuration records that govern how E-Records are secured and displayed to end users, joining the base administration entity to its translated (language-specific) display layer. The "_VL" suffix identifies it as a bilingual/MLS view that resolves translated columns at runtime based on the session language established through the USERENV('LANG') function.

Within the Oracle EBS reporting and integration architecture, this view behaves as a read-only presentation layer. It is the object that ad-hoc reports, Oracle Discoverer workbooks, BI Publisher data templates, and custom forms or OAF pages query when they require the administratively defined security sections and their localized names. Because it returns only the translation row matching the caller's current session language, it safely provides locale-appropriate DISPLAY_NAME values without requiring the report developer to join translation tables manually.

It should be noted that the ETRM documentation for the 12.2.2 environment records this view as "Not implemented in this database." This does not mean the view is invalid or obsolete; rather, the EDR – E-Records product was not installed or licensed in that particular instance. The view definition remains valid and is deployed wherever the EDR module is implemented.

Underlying Base Objects

The view is defined over two base tables, both owned by the EDR schema:

  • EDR_SEC_ADMIN_B — the base (non-translatable) administration table holding the core identity of each security administration record, including its section, event, document type, element, and tag attributes along with standard Who columns.
  • EDR_SEC_ADMIN_TL — the translation table holding the language-dependent DISPLAY_NAME for each section, keyed by SECTION_ID and LANGUAGE.

The two tables are joined on the common SECTION_ID column, with the translation side filtered by T.LANGUAGE = USERENV('LANG'). This pattern is the standard Oracle Applications MLS construct, and it is what earns the view its "_VL" designation. The view retains the ROWID of the base table as ROW_ID, allowing downstream tools to identify the underlying physical record.

Key Columns

  • ROW_ID — the ROWID of the corresponding EDR_SEC_ADMIN_B row; useful for identifying the physical record.
  • SECTION_ID — primary unique identifier linking the base and translation tables.
  • SECTION_NAME — internal name of the security administration section.
  • EVENT_NAME — the E-Records event to which the section applies.
  • DOCTYPE — document type associated with the section.
  • ELEMENT — the specific element or field the section governs.
  • TAG — identifier tag used to reference the element within the security configuration.
  • DISPLAY_NAME — the language-specific, user-facing label resolved from the translation table.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard Oracle Applications audit (Who) columns capturing creation and modification history.

Common Use Cases and Queries

The view is most commonly queried to populate LOVs, validate security section configuration, and produce localized administrative listings. A typical retrieval of all configured sections is:

SELECT section_id,
       section_name,
       event_name,
       doctype,
       element,
       tag,
       display_name
FROM   edr_sec_admin_vl
ORDER  BY section_name;

To inspect a single section by its identifier:

SELECT section_id, section_name, display_name, doctype
FROM   edr_sec_admin_vl
WHERE  section_id = :p_section_id;

Because the view honors USERENV('LANG'), the same query returns the correct localized DISPLAY_NAME automatically depending on the language of the connecting responsibility or session. Developers should be aware that if the requested language has no translation row in EDR_SEC_ADMIN_TL, the join returns no row for that section; a LEFT JOIN to the translation table may be preferable in diagnostic scripts where the base configuration must be confirmed regardless of localization. For any integration running under a non-installed language, verify that the EDR module is deployed and the desired language is registered before relying on the view.