Search Results ax_clauses




Overview
Explore in AI Chat

Overview

AX_CLAUSES 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. Its documented purpose is to store the clauses used by query chains. In the Global Accounting Engine, query chains drive the assembly of accounting rules and data retrieval logic; each chain is composed of one or more query tables, and AX_CLAUSES holds the individual predicate clauses that filter or constrain the rows retrieved from those tables. The table is classified as VALID in the ETRM data dictionary, and it is registered with a primary key constraint AX_CLAUSES_PK and a unique index AX_CLAUSES_U1.

From a heuristic Data Vault modeling perspective, the mined foreign-key structure suggests a satellite-leaning classification. This indicates the table primarily records descriptive, attribute-like detail about a parent business entity — in this case, the query chain and query table definitions held in AX_QUERY_TABLES — rather than acting as an independent hub of business keys or a pure link between two hubs. This classification is a modeling suggestion derived from the FK topology, not a formal Oracle designation.

Key Information Stored

AX_CLAUSES contains fifteen documented columns. The primary key is composite, defined by constraint AX_CLAUSES_PK over CLAUSE_NUMBER, APPLICATION_ID, QUERY_CHAIN_NAME, and TABLE_NUMBER. The same four columns form the unique index AX_CLAUSES_U1, making them the documented business-key candidates that uniquely identify a clause within a chain and table context.

The identifying columns are:

  • CLAUSE_NUMBER — the ordinal identifier for the clause within its query chain.
  • APPLICATION_ID — the application owning the query chain; also part of the foreign key to AX_QUERY_TABLES.
  • QUERY_CHAIN_NAME — the name of the query chain to which the clause belongs.
  • TABLE_NUMBER — the query table within the chain that the clause targets.

The substantive logic of each clause is captured by four columns: LOGIC_OPERATOR (the boolean connector such as AND or OR), LEFT_COLUMN (the left-hand column being tested), COMPARISON_OPERATOR (the operator such as =, >, or LIKE), and RIGHT_OPERAND_TYPE together with RIGHT_OP_TABLE and RIGHT_OP_COLUMN_VALUE, which describe the right-hand side of the comparison — whether it is a literal value, a column, or a reference to another table. Standard audit columns complete the structure: LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical use cases involve diagnosing why a query chain returns unexpected accounting data, reviewing the configured filter logic for an application, or migrating clause definitions between environments. A frequent reporting pattern joins AX_CLAUSES to AX_QUERY_TABLES to present readable chain definitions:

SELECT c.QUERY_CHAIN_NAME, c.TABLE_NUMBER, c.CLAUSE_NUMBER, c.LOGIC_OPERATOR, c.LEFT_COLUMN, c.COMPARISON_OPERATOR, c.RIGHT_OPERAND_TYPE, c.RIGHT_OP_COLUMN_VALUE FROM AX.AX_CLAUSES c WHERE c.APPLICATION_ID = :app_id AND c.QUERY_CHAIN_NAME = :chain ORDER BY c.TABLE_NUMBER, c.CLAUSE_NUMBER;

Analysts also query for clauses referencing another table through RIGHT_OP_TABLE to trace cross-table dependencies, and audit queries filter on LAST_UPDATE_DATE to identify clauses modified during a support window. Because the clause number is only unique within its application, chain, and table combination, ad hoc queries should always include all four key columns.

Related Objects

The most significant related object is AX_QUERY_TABLES, which is referenced by the foreign key AX_CLAUSES.APPLICATION_ID, QUERY_CHAIN_NAME, TABLE_NUMBER → AX_QUERY_TABLES. This parent-child relationship means AX_QUERY_TABLES defines the query tables available to a chain, while AX_CLAUSES supplies the filters applied to them. Clauses themselves point onward to further definitions via the RIGHT_OP_TABLE column, which typically resolves to another AX_QUERY_TABLES row. Related AX objects include AX_QUERY_CHAINS, which defines chain headers, and the broader AX rule and accounting definition tables that consume query chain output. Because AX_CLAUSES is owned by the AX schema, joins across schemas should be performed with fully qualified names or appropriate synonyms and grants. Any deletion or renumbering of clause rows must preserve the composite key integrity enforced by AX_CLAUSES_PK and AX_CLAUSES_U1.