Results for “use_security_function”

6 results




Overview
Explore in AI Chat

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

Overview

XLA_SUBLEDGERS_FVL is a foreign key lookup (FVL) view owned by the APPS schema in Oracle E-Business Suite, residing within the XLA – Subledger Accounting product. It presents a denormalized, user-facing representation of the base table XLA_SUBLEDGERS, enriching each subledger registration record with translated application names and journal source names. The suffix "FVL" follows the standard Oracle convention for views intended to expose a primary key plus descriptive flexfield-style lookup attributes, typically for use in forms, list-of-values (LOV) definitions, and reporting queries where readable descriptions are required instead of raw identifiers.

In the context of a search on control_account_type_code, this view is significant because it exposes the CONTROL_ACCOUNT_TYPE_CODE column directly from XLA_SUBLEDGERS. That column governs how a subledger's accounting is mapped to control accounts and drives downstream behavior in SLA account derivation and reconciliation to General Ledger. The view is documented as VALID in ETRM for 12.2.2, and the same definition logic applies under 12.1.1, since XLA_SUBLEDGERS is a foundational SLA table present in both releases.

Underlying Base Objects

The view text joins three documented objects:

Because both lookup targets are translation views/enhanced views (_TL/_VL), the join against J includes the language predicate, ensuring the returned description matches the session language rather than a fixed base language. ROWID is carried through from XLA_SUBLEDGERS, allowing the view to be treated as an updatable-style lookup in forms.

Key Columns

  • ROW_ID — the row identifier inherited from XLA_SUBLEDGERS.
  • APPLICATION_ID / APPLICATION_TYPE_CODE / APPLICATION_NAME — the owning subledger application, its type classification, and its translated name.
  • JE_SOURCE_NAME / USER_JE_SOURCE_NAME — the internal journal source code and its translated display name.
  • VALUATION_METHOD_FLAG — indicates whether the subledger supports valuation methods (e.g., for cost/valuation-aware accounting).
  • DRILLDOWN_PROCEDURE_NAME — the procedure invoked for drill-down navigation from SLA to the subledger transaction.
  • USE_SECURITY_FUNCTION — a derived flag (DECODE of SECURITY_FUNCTION_NAME to 'Y'/'N') indicating whether security is enforced.
  • ALC_ENABLED_FLAG — whether Accounting Local Currency processing is enabled for the subledger.
  • CONTROL_ACCOUNT_TYPE_CODE — the control account type classification, central to the original search. It determines the account type used when control accounts are derived for that subledger, and is a key column for validating posting and reconciliation configuration.
  • CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard audit columns.

Common Use Cases and Queries

Typical uses include listing all registered subledgers with readable names, auditing control account configuration, and filtering subledgers by security or ALC flags. For example, to inspect control account type assignments:

SELECT application_name, je_source_name, control_account_type_code, alc_enabled_flag FROM apps.xla_sublayers_fvl WHERE control_account_type_code IS NOT NULL ORDER BY application_name, je_source_name;

Because USER_JE_SOURCE_NAME is language-dependent, the view is well suited to LOV and report output where translated text is preferred. For integrations, the raw JE_SOURCE_NAME and APPLICATION_ID are available alongside the descriptions, avoiding a second lookup. Note that CONTROL_ACCOUNT_TYPE_CODE and the other flag columns originate solely from XLA_SUBLEDGERS; the view's joins affect only descriptive columns, so any query filtering on control account type effectively reads the base table configuration directly.