Search Results axis2_operator

Overview

RG_REPORT_STANDARD_AXES_VL is a seeded, read-only view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the RG (Application Report Generator) product, the historical component of EBS responsible for the definition, storage, and execution of standard reports and financial statement generator (FSG) style reports. The view presents report "standard axes", the pre-defined analytical dimensions (such as period, account, or company) that a report uses to slice, sequence, or filter the underlying data. It is a "VL" view, meaning it implements the standard Oracle multi-language pattern: it joins the base table to its translation table and restricts the translation row to the session language using USERENV('LANG'). The view is flagged as VALID in ETRM and is exposed to reporting and integration tooling as the developer-facing interface to standard axis definitions. Because it is a view over the transactional definition tables, it is queried rather than maintained directly; inserts and updates are performed against the underlying _B and _TL tables through the Application Report Generator forms or public APIs.

Underlying Base Objects

The ETRM metadata documents two referenced base objects, both exposed in APPS as synonyms:

• RG_REPORT_STANDARD_AXES_B — the base (non-translated) table holding the axis definition rows, including application, axis identifier, class, precedence, database column mapping, and the where-clause logic.
• RG_REPORT_STANDARD_AXES_TL — the translation table holding language-specific attributes, principally STANDARD_AXIS_NAME and DESCRIPTION.

The view joins these two objects on STANDARD_AXIS_ID and filters AXT.LANGUAGE = USERENV('LANG'), guaranteeing that each axis appears exactly once, in the language of the running session. The AXS alias supplies all descriptive, structural, and audit columns; the AXT alias supplies the translatable name and description. This B/TL join is the canonical Oracle EBS MLS access pattern and explains why the view is the appropriate object for external queries: it hides the language join and returns only one row per axis per session.

Key Columns

• APPLICATION_ID — the owning application of the axis definition.
• STANDARD_AXIS_ID — the primary identifier and the join key between the base and translation records.
• STANDARD_AXIS_NAME, DESCRIPTION — the translated, user-visible labels selected for the session language.
• CLASS — categorizes the axis for report-generation purposes.
• DISPLAY_IN_STANDARD_LIST_FLAG — controls whether the axis appears in the standard selection list in the RG user interface.
• PRECEDENCE_LEVEL — determines ordering when multiple axes are applied.
• DATABASE_COLUMN — the physical or logical column to which the axis maps.
• SIMPLE_WHERE_NAME — the name of a stored, predefined where-clause fragment applied when the axis is used. This is the column matched by the search term "simple_where_name"; it identifies the reusable predicate used to filter report output for the axis.
• PERIOD_QUERY — indicates period-based query behavior for the axis.
• STANDARD_AXIS1_ID, AXIS1_OPERATOR, STANDARD_AXIS2_ID, AXIS2_OPERATOR, CONSTANT — define the operand/operator/constant expression that composes the axis predicate.
• VARIANCE_FLAG, SIGN_FLAG — govern variance reporting and sign treatment.
• Audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) support change tracking.

Common Use Cases and Queries

Typical uses include auditing axis configuration, diagnosing report filtering behavior, and driving integrations or custom reports that need the axis-to-where-clause mapping. A query filtered on the searched column might read:

• SELECT standard_axis_id, standard_axis_name, simple_where_name, database_column FROM rg_report_standard_axes_vl WHERE simple_where_name IS NOT NULL;
• SELECT standard_axis_name, class, precedence_level FROM rg_report_standard_axes_vl WHERE display_in_standard_list_flag = 'Y' ORDER BY precedence_level;
• SELECT standard_axis_name, period_query, variance_flag, sign_flag FROM rg_report_standard_axes_vl WHERE application_id = :app_id;

Because the view enforces the MLS join, these queries require no additional language handling, making it the preferred access path in both 12.1.1 and 12.2.2.