Results for “ax_rules”

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

Overview

AX_RULES is a table owned by the AX schema within the Oracle E-Business Suite Global Accounting Engine (AX) product. Its documented purpose is to store archived rule sets for an application. In the context of the Global Accounting Engine, rule sets define the transformation logic that maps subledger accounting events into accounting entries, and AX_RULES serves as the repository for those rule-set headers once they are archived or versioned against a specific application.

From a dimensional modeling perspective, the mined foreign key structure classifies this object as hub-leaning. This classification is offered as a modeling suggestion rather than a documented attribute: AX_RULES behaves as a central reference point for a stable business concept (a rule set), identified by a surrogate key and referenced by dependent detail rows in AX_RULE_LINES. It is not a transactional fact and not a pure descriptive satellite, since child lines depend on it directly.

Key Information Stored

The table is documented with twelve physical columns and a single unique index, AX_RULES_U1, on RULE_ID. The primary key constraint AX_RULES_PK also covers RULE_ID, so the surrogate primary key and the business-key candidate coincide on this column.

• RULE_ID — Surrogate primary key and unique-index column; the identifier propagated to child rule lines.
• APPLICATION_ID — Identifies the application whose rule set is archived; establishes the owning context of each rule set.
• RULE_NAME — The user-facing name of the rule set.
• RULE_VERSION, RULE_SUB_VERSION, RULE_REVISION — Versioning attributes that distinguish successive archived editions of the same logical rule set.
• PROCESSED_FLAG — Indicates whether the rule set has been processed, supporting batch or concurrent-program driven workflows.
• CREATION_DATE, CREATED_BY — Standard audit attributes recording initial insert.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard audit attributes recording the most recent modification and the login under which it occurred.

The prominent presence of creation and update audit columns alongside version columns is consistent with an archival design in which rows are retained and versioned rather than overwritten.

Common Use Cases and Queries

Typical reporting and diagnostic scenarios revolve around identifying which rule set was active or archived for a given application and version, and reconciling processed versus unprocessed rule sets. A representative join pattern retrieves rule-set headers with their line detail:

• Listing archived rule sets for an application: filter AX_RULES by APPLICATION_ID and order by RULE_VERSION, RULE_SUB_VERSION, RULE_REVISION to reconstruct the version history.
• Audit reporting: select RULE_ID, RULE_NAME, CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE and LAST_UPDATED_BY to trace who created or modified a rule set.
• Process monitoring: select rows where PROCESSED_FLAG is null or indicates incomplete processing, to identify rule sets awaiting batch processing.
• Header-to-line reconciliation: join AX_RULES to AX_RULE_LINES on RULE_ID to confirm that each archived rule set retains its associated lines.

Because RULE_ID is both the primary key and the unique business-key candidate, it is the correct join column for all downstream queries.

Related Objects

The documented foreign key relationship establishes AX_RULE_LINES as the principal dependent object. AX_RULE_LINES.RULE_ID references AX_RULES, forming a header-to-line (parent-to-child) relationship keyed on RULE_ID. This is the most significant and only documented direct reference in the supplied metadata.

Broader AX Global Accounting Engine objects that commonly participate in the same rule-processing flow — such as rule-set line definitions, accounting event and journal generation components — should be treated as adjacent rather than confirmed dependencies unless a foreign key is documented. Practically, analysis of AX_RULES should proceed through AX_RULES_PK/RULE_ID as the anchor, with AX_RULE_LINES joined on RULE_ID for detail, and APPLICATION_ID used to constrain results to the relevant application context.