Results for “sign_flag”

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

Overview

RG_REPORT_STANDARD_AXES_B is a foundational configuration table in the Oracle E-Business Suite Application Report Generator (RG) module, present in both 12.1.1 and 12.2.2 environments. The table stores the definitions of amount types — the standard axes — that report authors use to construct the rows and columns of Financial Statement Generator (FSG) and RG reports. Each row describes a reusable axis definition, such as a period-to-date balance, a year-to-date balance, a beginning balance, or a variance calculation, along with the components and operators needed to derive that amount at runtime.

Because the table is entirely configuration and definition driven, it is populated at implementation and maintained by the report administrator rather than by transactional activity. Treating the underlying FK structure as a modeling heuristic, the object leans toward a hub classification within a Data Vault-style model: it holds the core identity of an amount-type definition (STANDARD_AXIS_ID) and acts as the anchor referenced by both its own recursive relationships and by the translation table RG_REPORT_STANDARD_AXES_TL. This is a modeling suggestion, not a documented Data Vault implementation.

Key Information Stored

RG_REPORT_STANDARD_AXES_B contains 21 documented columns. The most significant for understanding and extending the model are:

• STANDARD_AXIS_ID — the surrogate primary key for the row, uniquely identifying each amount type. It is the column named in the RG_REPORT_STANDARD_AXES_B_PK primary key.
• APPLICATION_ID — identifies the Oracle application context to which the axis belongs, scoping the definition across the EBS data model.
• CLASS — the functional category or class of the amount type, guiding how the axis is interpreted by the report engine.
• DISPLAY_IN_STANDARD_LIST_FLAG — controls whether the axis appears in the standard selection list presented to report authors.
• PRECEDENCE_LEVEL — the order of evaluation when multiple axes interact.
• DATABASE_COLUMN — maps the axis to a specific database column used as its source value.
• SIMPLE_WHERE_NAME and PERIOD_QUERY — the stored predicates and period logic that supply the amount at runtime.
• STANDARD_AXIS1_ID / STANDARD_AXIS2_ID and AXIS1_OPERATOR / AXIS2_OPERATOR — recursive references to two component axes plus the operators combining them, enabling derived amounts such as variances.
• CONSTANT — a fixed value used in axis computation.
• VARIANCE_FLAG and SIGN_FLAG — control variance behavior and the arithmetic sign applied to the derived amount.
• ZD_EDITION_NAME — the edition column used for the 12.2.2 online patching / editioning infrastructure, and part of the unique index RG_REPORT_STANDARD_AXES_B_U1 along with STANDARD_AXIS_ID.

Standard audit columns LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATION_DATE, and CREATED_BY are also present and follow EBS conventions. The unique index RG_REPORT_STANDARD_AXES_B_U1 (STANDARD_AXIS_ID, ZD_EDITION_NAME) represents the business-key candidate, whereas STANDARD_AXIS_ID alone serves as the surrogate primary key.

Common Use Cases and Queries

Typical usage centers on enumerating available amount types, tracing dependencies between derived axes, and auditing definition changes. A simple listing of selectable axes:

• SELECT standard_axis_id, class, database_column FROM rg_report_standard_axes_b WHERE display_in_standard_list_flag = 'Y';
• Dependency analysis, joining an axis to its component axes via the recursive FKs on STANDARD_AXIS1_ID and STANDARD_AXIS2_ID to reconstruct variance or rolling calculations.
• Change auditing against the audit columns to identify recently modified amount types.
• Reporting joined to RG_REPORT_STANDARD_AXES_TL to retrieve translated axis names for the user's language.

Queries should generally filter on ZD_EDITION_NAME in 12.2.2 to respect the editioning model.

Related Objects

The most significant related objects, derived from documented FK relationships, are:

• RG_REPORT_STANDARD_AXES_B (self-referential) via STANDARD_AXIS1_ID and STANDARD_AXIS2_ID — links an axis to its component axes for derived amounts.
• RG_REPORT_STANDARD_AXES_TL via STANDARD_AXIS_ID — the translation table supplying language-specific names and descriptions.
• RG_REPORT_STANDARD_AXES_TL (column STANDARD_AXIS_ID) joins to the base table on the same key.

Together, the base table and its translation counterpart form the axis-definition core consumed by RG and FSG report processing.