Results for “axis_seq_high”

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

Overview

RG_REPORT_CALCULATIONS is a table within the RG (Application Report Generator) schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the calculation definitions applied to rows and columns of reports generated by the Application Report Generator. In practical terms, this table is the repository that governs how report values are derived: it records which axis positions participate in a calculation, the arithmetic operator applied, and any constant or contextual qualifier used in the computation.

Within the RG data model, RG_REPORT_CALCULATIONS functions as a link entity. It resolves the many-to-many relationship between report axis definitions (stored in RG_REPORT_AXES) and the individual calculation steps applied along those axes. Because the table carries descriptive and operational attributes such as OPERATOR and CONSTANT in addition to its foreign key columns, a Data Vault modeling exercise would likely classify it as a link with attached descriptive attributes rather than a pure satellite. All records are scoped to a specific report application through APPLICATION_ID, and the table is audited through the standard EBS WHO columns.

Key Information Stored

The table is defined with 31 columns in the documented 12.2.2 schema. The most significant columns are:

• APPLICATION_ID — identifies the Oracle application context to which the report calculation belongs; a primary scoping attribute for multi-application environments.
• AXIS_SET_ID — foreign key to RG_REPORT_AXES, identifying the axis set on which the calculation operates.
• AXIS_SEQ — the sequence position of the axis entry being calculated; this is the target row or column position that receives the computed result.
• CALCULATION_SEQ — sequence number distinguishing multiple calculation steps defined for the same axis entry.
• OPERATOR — the arithmetic or aggregation operator applied to the referenced axis range (for example addition, subtraction, percentage, or ratio).
• AXIS_SEQ_LOW and AXIS_SEQ_HIGH — the lower and upper bounds of the axis range from which operands are drawn.
• AXIS_NAME_LOW and AXIS_NAME_HIGH — display or label names corresponding to the low and high axis bounds, useful for reporting and validation.
• CONSTANT — a fixed numeric value used in the calculation when the definition calls for a literal operand.
• CONTEXT — an indicator or qualifier describing the context in which the calculation applies.
• ATTRIBUTE1 through ATTRIBUTE15 — the standard EBS descriptive flexfield columns, available for extensible, site-specific calculation metadata.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATION_DATE, CREATED_BY — the standard WHO audit columns tracking record provenance and change history.

The primary key RG_REPORT_CALCULATIONS_PK is a composite key over (AXIS_SET_ID, AXIS_SEQ, CALCULATION_SEQ), which unambiguously identifies each calculation step within an axis set. The surrogate key here is effectively the composite of these three columns; business-key candidates are limited because AXIS_SET_ID and AXIS_SEQ are also foreign key references to RG_REPORT_AXES.

Common Use Cases and Queries

Typical scenarios include auditing report calculation definitions, cloning calculations between report definitions, and troubleshooting incorrect totals or ratios in generated reports. A common query pattern retrieves all calculations and their target axis entries for a given axis set:

• Join RG_REPORT_CALCULATIONS to RG_REPORT_AXES on AXIS_SET_ID and AXIS_SEQ to resolve operand ranges and confirm the calculated row or column.
• Filter by APPLICATION_ID and AXIS_SET_ID to produce a report-definition extract for migration or documentation.
• Aggregate by OPERATOR to analyze calculation complexity across report definitions.
• Query the ATTRIBUTE flexfield columns where site-specific calculation logic has been configured.
• Compare LAST_UPDATE_DATE against report generation timestamps to determine whether a calculation change preceded a reported discrepancy.

Related Objects

The table is tightly coupled with the following objects:

• RG_REPORT_AXES — referenced three times: AXIS_SET_ID and AXIS_SEQ, AXIS_SET_ID and AXIS_SEQ_HIGH, and AXIS_SET_ID and AXIS_SEQ_LOW. This is the primary parent table defining the rows and columns on which calculations operate.
• RG_REPORT_CALCULATIONS_PK — the composite primary key constraint over (AXIS_SET_ID, AXIS_SEQ, CALCULATION_SEQ).
• RG_REPORT_DEFINITIONS / RG_REPORT_SETS — report-level definitions that ultimately consume the calculations defined here through their axis sets.
• FND_APPLICATION — joined via APPLICATION_ID to resolve the owning application name for reporting and diagnostics.
• FND_FLEX_VALUES — used in conjunction with the ATTRIBUTE1–15 flexfield columns when descriptive flexfields are enabled for this table.

Because no public APIs or views are documented specifically for RG_REPORT_CALCULATIONS in the ETRM metadata, integration is generally performed through direct SQL against the RG schema, and any customizations should preserve the composite primary key and foreign key integrity to RG_REPORT_AXES.