Results for “security_enabled_flag”

50+ results




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

Overview

FND_DESCR_FLEX_COLUMN_USAGES is an Application Object Library (FND) table that resides in the APPLSYS schema and stores the correspondences between application table columns and descriptive flexfield segments. In Oracle EBS 12.1.1 and 12.2.2, this table is a critical metadata repository describing how the columns of a descriptive flexfield-enabled application table are mapped to the flexfield's segments, including their display characteristics, validation, and defaulting behavior.

The table is scoped by the combination of the owning APPLICATION_ID, the descriptive flexfield name, and the DESCRIPTIVE_FLEX_CONTEXT_CODE, which together identify the specific segment set to which each column usage applies. Based on the foreign key topology, in which this table references FND_DESCR_FLEX_CONTEXTS and FND_FLEX_VALUE_SETS while being referenced by its translation table, the heuristic Data Vault classification is satellite-leaning. In modeling terms, the composite key formed by application, flexfield name, context code, and application column name acts as a hub-like identifier, and the descriptive attributes such as display and required flags function as satellite attributes attached to that identifier.

Key Information Stored

The table contains 25 documented columns. Its documented primary key, FND_DESC_FLEX_COLUMN_USAGES_PK, comprises APPLICATION_ID, DESCRIPTIVE_FLEXFIELD_NAME, DESCRIPTIVE_FLEX_CONTEXT_CODE, and APPLICATION_COLUMN_NAME. These same four columns also form the leading portion of unique indexes FND_DESC_FLEX_COL_USAGES_U1 and FND_DESC_FLEX_COL_USAGES_U2, making them the documented business-key candidates. The most important columns include:

Common Use Cases and Queries

A primary use case is identifying which table columns store which descriptive flexfield segments for a given context, which is essential when building SQL to retrieve flexfield values. The following pattern joins the usage table to its context definition:

  • Query column usages by context: SELECT APPLICATION_COLUMN_NAME, END_USER_COLUMN_NAME, FLEX_VALUE_SET_ID FROM FND_DESCR_FLEX_COLUMN_USAGES WHERE DESCRIPTIVE_FLEXFIELD_NAME = :flexfield AND DESCRIPTIVE_FLEX_CONTEXT_CODE = :context;
  • Determine required versus optional segments using REQUIRED_FLAG and ENABLED_FLAG.
  • Resolve validation value sets through a join to FND_FLEX_VALUE_SETS on FLEX_VALUE_SET_ID.

Reporting scenarios include generating documentation of flexfield configurations, auditing which columns are displayed or secured, and reconciling segment metadata during upgrades from 12.1.1 to 12.2.2.

Related Objects

The following objects are most significant in relation to this table, based on the documented foreign key and relationship data:

  • FND_DESCR_FLEX_CONTEXTS — parent defining the contexts; joined on APPLICATION_ID, DESCRIPTIVE_FLEXFIELD_NAME, and DESCRIPTIVE_FLEX_CONTEXT_CODE.
  • FND_FLEX_VALUE_SETS — validation source; joined on FLEX_VALUE_SET_ID.
  • FND_DESCR_FLEX_COL_USAGE_TL — translation table referencing this table on APPLICATION_ID, DESCRIPTIVE_FLEXFIELD_NAME, DESCRIPTIVE_FLEX_CONTEXT_CODE, and APPLICATION_COLUMN_NAME.
  • FND_DESCR_FLEX_SEGMENTS — segment definitions that underlie the column usages.
  • FND_DESCRIPTIVE_FLEXS — the flexfield registration referenced by DESCRIPTIVE_FLEXFIELD_NAME.