Results for “standard_axis_id”

50+ results




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

Overview

RG_REPORT_STANDARD_AXES_TL is the translation table for RG_REPORT_STANDARD_AXES_B within the Oracle E-Business Suite Application Report Generator (RG) module. The RG product provides the historical, developer-oriented report generation framework that predates Oracle Reports and XML Publisher, and standard axes represent the reusable row, column, page, and dimension definitions used when constructing matrix-style reports. Because Oracle EBS is deployed in multilingual environments, every user-facing name and description of a standard axis must be stored once per installed language, which is exactly the purpose of this _TL table.

In Data Vault modeling terms, the FK relationship and the structure of the table suggest a satellite-leaning classification. The parent RG_REPORT_STANDARD_AXES_B table functions as the hub holding the language-independent axis identity (STANDARD_AXIS_ID), while this translation table carries the descriptive, language-dependent attributes keyed to that hub plus the language. This classification is a heuristic derived from the FK topology rather than a formally declared Oracle warehouse design.

Key Information Stored

The table contains eleven documented columns, of which the most operationally significant are the following:

  • STANDARD_AXIS_ID — the surrogate identifier inherited from the base table; it is the foreign key linking each translation row back to RG_REPORT_STANDARD_AXES_B.
  • LANGUAGE — the NLS language code (for example US, DE, JA) that determines which translation a session retrieves.
  • SOURCE_LANG — indicates the source language from which the translation was derived, used by the translation-workbench utilities.
  • STANDARD_AXIS_NAME — the translated display name of the standard axis; this is a business-key candidate because it is unique per language.
  • DESCRIPTION — the translated long description of the standard axis.
  • ZD_EDITION_NAME — the editioning column introduced by the EBS 12.2 online patching (Edition-Based Redefinition) architecture, allowing multiple editions of the row to coexist during an upgrade cycle.
  • Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN — capture who created or last modified each translated row.

The primary key RG_REPORT_STANDARD_AXES_TL_PK is composed of STANDARD_AXIS_ID and LANGUAGE. Two unique indexes further constrain the data: RG_REPORT_STANDARD_AXES_TL_U1 on (STANDARD_AXIS_ID, LANGUAGE, ZD_EDITION_NAME) and RG_REPORT_STANDARD_AXES_TL_U2 on (STANDARD_AXIS_NAME, LANGUAGE, ZD_EDITION_NAME). U2 is the true business-key candidate, since it guarantees that no two standard axes share the same translated name within a language.

Common Use Cases and Queries

Developers and DBAs typically query this table when investigating why an axis description displays in the wrong language, or when building custom reports that must join translated axis names to the base report definitions. A representative query joining the translation table to its base table is:

  • SELECT b.standard_axis_id, t.standard_axis_name, t.description FROM rg_report_standard_axes_b b, rg_report_standard_axes_tl t WHERE b.standard_axis_id = t.standard_axis_id AND t.language = USERENV('LANG');

Other common patterns include verifying that every standard axis in the base table has a translation in every installed language (a completeness check), auditing who last changed a translated name using LAST_UPDATED_BY and LAST_UPDATE_DATE, and extracting axis metadata for migration or documentation projects. Because the table participates in EBR, edition-aware queries may also filter on ZD_EDITION_NAME when diagnosing online-patching issues in a 12.2.2 environment.

Related Objects

The most significant related objects are:

  • RG_REPORT_STANDARD_AXES_B — the base table holding the language-independent axis definition; joined on STANDARD_AXIS_ID.
  • RG_REPORT_STANDARD_AXES_TL_PK — the primary key constraint enforcing uniqueness of STANDARD_AXIS_ID and LANGUAGE.
  • RG_REPORT_STANDARD_AXES_TL_U1 and RG_REPORT_STANDARD_AXES_TL_U2 — the unique indexes described above.
  • The parent report definition tables in the RG schema that reference standard axes, including the axis-usage and report-layout tables that consume STANDARD_AXIS_ID.
  • The Oracle Translation (FND) workbench utilities that maintain _TL tables and SOURCE_LANG values.
  • Any custom or seeded concurrent programs and reports that render axis names for end users in a specific session language.