Search Results mtl_flex_context




Overview
Explore in AI Chat

Overview

MTL_FLEX_CONTEXT is an Inventory (INV) module table that serves as the context mapping table for Lot and Serial attribute Descriptive Flexfields (DFF). In Oracle EBS 12.1.1 and 12.2.2, Descriptive Flexfields allow customers to extend standard product functionality by defining additional attribute columns that are not part of the base application schema. For lot and serial controlled items, Oracle seeds and maintains flexfield structures whose context-sensitive segments must be resolved at runtime. MTL_FLEX_CONTEXT stores the association between a flexfield context value and the underlying Oracle column that physically holds the context segment, enabling the application to map a user-selected context code to its corresponding database column.

From a Data Vault modeling perspective, the heuristic classification mined from the foreign key structure treats this object as standalone, suggesting it functions as a reference or lookup entity rather than a hub, link, or satellite in a dimensional or Data Vault warehouse design. This classification reflects its limited, self-contained relationships within the EBS schema and its role as a configuration mapping table rather than a transactional fact carrier.

Key Information Stored

The table is keyed by the composite primary key MTL_FLEX_CONTEXT_PK, defined across ORGANIZATION_ID, DESCRIPTIVE_FLEXFIELD_NAME, CONTEXT_COLUMN_NAME, and CONTEXT_COLUMN_VALUE_ID. These four columns together constitute both the surrogate-level uniqueness constraint and the principal business-key candidate, since no separate unique index is documented beyond the primary key definition.

  • ORGANIZATION_ID — Identifies the inventory organization to which the flexfield context mapping applies, supporting multi-org partitioning of flexfield definitions.
  • DESCRIPTIVE_FLEXFIELD_NAME — The internal application name of the descriptive flexfield (for example, lot or serial attribute flexfields), scoping the context definition to a specific flexfield.
  • CONTEXT_COLUMN_NAME — The name of the database column that stores the context segment value; this is the attribute most relevant to users searching for "context_column_name."
  • CONTEXT_COLUMN_VALUE_ID — A numeric identifier for the context value, used to bind the context to its physical column representation.
  • DESCRIPTIVE_FLEX_CONTEXT_CODE — The human-readable context code presented to and selected by users in the flexfield UI.
  • CATEGORY_SET_ID — Associates a category set relevant to the flexfield context, influencing validation and segment behavior.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard EBS audit columns capturing who created and modified each mapping and when.
  • REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — Concurrent program tracking columns identifying the process that last touched the row.

Common Use Cases and Queries

Administrators and developers query MTL_FLEX_CONTEXT to diagnose flexfield behavior, resolve which physical column stores a given context value, or audit flexfield configuration across organizations. A typical pattern retrieves all context column mappings for a specific flexfield:

  • SELECT context_column_name, descriptive_flex_context_code, organization_id FROM mtl_flex_context WHERE descriptive_flexfield_name = :flex_name;
  • Joining to organization and flexfield definition tables to produce a configuration report of lot/serial DFF contexts.
  • Reporting on CATEGORY_SET_ID associations to validate category-based segment behavior.
  • Audit queries using LAST_UPDATE_DATE and LAST_UPDATED_BY to track recent configuration changes.

Related Objects

As a standalone reference table, MTL_FLEX_CONTEXT has limited foreign key dependencies but logically relates to several inventory and flexfield objects: