Results for “variable_id”

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

Overview

RG_DSS_SYSTEM_VARIABLES_V is a reporting view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the RG product family (Application Report Generator) and is documented in the E-Business Suite Technical Reference Manual (ETRM) with the description "10SC ONLY." The object carries a VALID status in the data dictionary, confirming it is a supported, compiled view available to the application and to custom extension work.

The view presents a denormalized, join-based projection over the RG system-variable configuration tables. Its functional role is to expose the linkage between a system registered in the Report Generator repository and the variables associated with that system, while resolving the numeric variable identifier into a human-readable variable name. In practice, the view is consumed by reporting and integration components that need to enumerate the system variables applicable to a given RG system without navigating the raw base tables.

Underlying Base Objects

The ETRM documents two referenced base objects, both exposed to the view through synonyms in the APPS schema:

• RG_DSS_SYSTEM_VARIABLES — the driving table, aliased SVR in the view text. It holds the system-variable assignment rows and supplies the row identifier, system identifier, variable identifier, system variable identifier, audit columns, and the descriptive flexfield context and attribute columns.
• RG_DSS_VARIABLES — the reference table, aliased VAR. It supplies the variable NAME, which is projected as VARIABLE_NAME.

The two tables are joined on VARIABLE_ID, which is the common key linking a variable definition to its assignment on a system. Because the view is defined over RG_DSS_SYSTEM_VARIABLES, the view is by default updatable only in the sense of the ROWID pseudocolumn exposed as ROW_ID; standard practice is to treat it as a query-only reporting object rather than a DML target.

Key Columns

The view exposes a compact set of identifying columns plus a standard descriptive flexfield block:

• ROW_ID — the ROWID of the underlying RG_DSS_SYSTEM_VARIABLES row, used for direct-row addressing.
• SYSTEM_ID — identifies the RG system to which the variable assignment belongs.
• VARIABLE_ID — the foreign key to the RG variable definition; the join key between the two base tables.
• VARIABLE_NAME — the descriptive name of the variable, sourced from RG_DSS_VARIABLES.NAME.
• SYSTEM_VARIABLE_ID — the surrogate identifier for the system-variable assignment itself; this is the column most commonly used as the primary lookup key when a user searches for "system_variable_id."
• Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN provide who/when tracking consistent with EBS conventions.
• CONTEXT and ATTRIBUTE1 through ATTRIBUTE15 — the descriptive flexfield segments, enabling customer-defined attributes to be carried through the view.

Common Use Cases and Queries

Typical scenarios include verifying which variables are assigned to a system prior to running or migrating Report Generator definitions, auditing flexfield attribute usage, and resolving a known SYSTEM_VARIABLE_ID back to its owning system and variable name.

Retrieve a single assignment by its surrogate key:

• SELECT system_variable_id, system_id, variable_id, variable_name FROM apps.rg_dss_system_variables_v WHERE system_variable_id = :p_id;

Enumerate all variables for a given system:

• SELECT variable_name, variable_id, creation_date FROM apps.rg_dss_system_variables_v WHERE system_id = :p_system ORDER BY variable_name;

Audit recently modified assignments and any populated flexfield attributes:

• SELECT system_variable_id, system_id, last_updated_by, last_update_date FROM apps.rg_dss_system_variables_v WHERE last_update_date > :p_since ORDER BY last_update_date DESC;

Because the view joins two base tables, no index other than those on RG_DSS_SYSTEM_VARIABLES and RG_DSS_VARIABLES can be added directly to the view; queries should filter on SYSTEM_ID, VARIABLE_ID, or SYSTEM_VARIABLE_ID so the optimizer can push predicates to the base tables.