Search Results ax_arithmetic_expr




Overview
Explore in AI Chat

Overview

AX_ARITHMETIC_EXPR is a table in the AX schema, owned by the Global Accounting Engine (AX) product within Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the arithmetic expressions that are applied by amount structures during the Global Accounting Engine's transformation and translation processing. Amount structures define how balances are derived, translated, and posted; the expressions held in this table supply the actual operators, operand types, and source references that the engine evaluates at runtime to compute resulting amounts.

In Data Vault modeling terms, the heuristic classification of this object is satellite-leaning. This suggests it should be modeled as descriptive context attached to a parent structure hub rather than as an independent hub or as a link resolving many-to-many relationships. Its grain is defined by the combination of books, application, translation scheme, plan, structure, and expression identifiers, all of which point back to a single owning structure.

Key Information Stored

The primary key is AX_ARITHMETIC_EXPR_PK, a composite of SET_OF_BOOKS_ID, APPLICATION_ID, TRANSLATION_SCHEME, PLAN_NAME, STRUCTURE_NUMBER, STRUCTURE_TYPE, and EXPRESSION_NUMBER. These same columns also form the unique index AX_ARITHMETIC_EXPR_U1, making them the business-key candidates. The unique index is effectively a business-key alternate to the declared constraint, and EXPRESSION_NUMBER provides the ordinal that sequences multiple expressions within a given structure.

The most significant data-bearing columns include:

  • OPERATOR — the arithmetic operator applied within the expression, such as addition, subtraction, or multiplication.
  • OPERAND_TYPE — classifies the operand, indicating whether the source is a table column, a constant, or another derived value.
  • SOURCE_TABLE — the database table from which the operand value is drawn.
  • SOURCE_COLUMN_VALUE — the specific column or literal value referenced by the operand.
  • SET_OF_BOOKS_ID — the ledger context in which the expression is valid.
  • APPLICATION_ID — the owning application of the structure.
  • TRANSLATION_SCHEME — the translation scheme to which the structure belongs.
  • PLAN_NAME — the plan grouping the structure.
  • STRUCTURE_NUMBER and STRUCTURE_TYPE — identify the parent amount structure.
  • EXPRESSION_NUMBER — the sequence position of the expression.

Standard audit columns LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN are also present, bringing the documented column count to sixteen.

Common Use Cases and Queries

Typical use cases include auditing the arithmetic logic behind a specific amount structure, tracing which source tables and columns feed a derived balance, and reporting on expression sequencing for migration or configuration reviews. A representative query joins the expressions to their parent structure:

SELECT e.STRUCTURE_NUMBER, e.EXPRESSION_NUMBER, e.OPERATOR,
       e.OPERAND_TYPE, e.SOURCE_TABLE, e.SOURCE_COLUMN_VALUE
FROM   AX.AX_ARITHMETIC_EXPR e
WHERE  e.SET_OF_BOOKS_ID = :p_sob_id
AND    e.APPLICATION_ID = :p_app_id
ORDER BY e.STRUCTURE_NUMBER, e.EXPRESSION_NUMBER;

Because the table is keyed by expression number, reports should always order by STRUCTURE_NUMBER and EXPRESSION_NUMBER to reconstruct the evaluation sequence correctly. Configuration comparisons across ledgers can be performed by selecting the same structure under differing SET_OF_BOOKS_ID values.

Related Objects

The primary relationship is a foreign key to AX_STRUCTURES on the columns SET_OF_BOOKS_ID, APPLICATION_ID, TRANSLATION_SCHEME, PLAN_NAME, STRUCTURE_TYPE, and STRUCTURE_NUMBER. This makes AX_STRUCTURES the parent object that governs the lifecycle of each expression row.

  • AX_STRUCTURES — parent structure definition referenced by the composite foreign key.
  • AX_AMOUNT_STRUCTURES / amount structure definitions — the broader configuration objects that consume these expressions.
  • Global Accounting Engine concurrent programs — processing programs that evaluate these expressions during translation and posting.
  • AX schema reporting views — queries that join expression data to structure and ledger metadata.

Because the metadata documents only the AX_STRUCTURES foreign key, additional dependents should be confirmed against the implementation's actual schema before being relied upon in custom reporting.