Results for “variable_name”

2 results




Overview
Explore in AI Chat

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

Overview

FND_ENV_CONTEXT is a table owned by the APPLSYS schema within the FND – Application Object Library product of Oracle E-Business Suite. As documented in the ETRM metadata for releases 12.1.1 and 12.2.2, this object stores the environment name and value pairs associated with each concurrent process executed in the EBS environment. In practical terms, it functions as a runtime context repository: whenever a concurrent program is launched, the concurrent manager captures the session-specific environment variables — such as request identifiers, user identifiers, organization identifiers, or profile-derived values — and persists them against the owning concurrent process identifier.

From a data modeling perspective, the ETRM documentation classifies FND_ENV_CONTEXT as a standalone object, meaning no foreign key constraints are mined from its structure. Applying a heuristic Data Vault interpretation, the table is best modeled as a satellite, since it holds descriptive attribute-style content (VARIABLE_NAME and VALUE) that qualifies the parent concurrent process rather than representing an independent business entity or an associative relationship between two hubs.

Key Information Stored

The documented physical schema contains only three columns, which makes the table compact but strategically important:

  • CONCURRENT_PROCESS_ID — Identifies the concurrent process instance to which the environment context belongs. This is a key component in both the primary key and the unique index.
  • VARIABLE_NAME — The name of the environment variable or context setting captured for that process, such as a session pattern or environment token.
  • VALUE — The corresponding value assigned to the named variable during the execution of the concurrent process.

The surrogate primary key is defined by the constraint FND_ENV_CONTEXT_PK over the composite of CONCURRENT_PROCESS_ID and VARIABLE_NAME. The unique index FND_ENV_CONTEXT_U1 covers the same two columns, confirming that the business-key candidate is the combination of process identifier and variable name. The VALUE column is non-key and purely descriptive. This two-column composite key means a single concurrent process can carry many named environment entries, one row per variable.

Common Use Cases and Queries

The primary use case is diagnostic and operational: DBAs and Oracle support engineers inspect rows for a given concurrent process to determine which environment settings were in effect during a run, which is essential when reproducing errors or validating context-sensitive behavior. A typical retrieval pattern is:

  • SELECT variable_name, value FROM applsys.fnd_env_context WHERE concurrent_process_id = :proc_id ORDER BY variable_name;
  • SELECT c.concurrent_process_id, e.variable_name, e.value FROM applsys.fnd_env_context e JOIN fnd_concurrent_processes c ON c.concurrent_process_id = e.concurrent_process_id WHERE e.variable_name = 'PATTERN';

Reporting scenarios include searching for all processes that executed under a particular environment value, correlating context values with concurrent request outcomes, and auditing which variables were recorded across a batch window. Because the table is small and keyed efficiently, point lookups by CONCURRENT_PROCESS_ID and VARIABLE_NAME are fast, making it suitable for support-driven queries rather than bulk analytics.

Related Objects

Although FND_ENV_CONTEXT is documented as standalone with no enforced foreign keys, it logically depends on the concurrent processing framework. The most significant related objects include:

  • FND_CONCURRENT_PROCESSES — joined on CONCURRENT_PROCESS_ID, providing the process-level context for each environment entry.
  • FND_CONCURRENT_REQUESTS — links the process to the submitted request, enabling end-to-end tracing.
  • FND_CONCURRENT_PROGRAMS — identifies the program definition associated with the process.
  • FND_CONCURRENT_QUEUES — describes the manager and queue under which the process ran.
  • FND_ENV_CONTEXT_PK / FND_ENV_CONTEXT_U1 — the primary key constraint and unique index that enforce row uniqueness.

Together these objects allow administrators to reconstruct the complete execution context of any concurrent process, with FND_ENV_CONTEXT supplying the environment-level attributes.