Results for “ax_rule_lines”

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

Overview

The AX.AX_RULE_LINES table is a component of the Oracle E-Business Suite Global Accounting Engine (AX) module. Its documented description in the ETRM metadata is "Components of a rule set," indicating that it stores the individual line-level elements that make up rule set definitions consumed by the Global Accounting Engine during transaction processing and accounting event generation. In EBS 12.1.1 and 12.2.2, the AX schema underpins the accounting engine that derives accounting entries from subledger and general ledger events, and AX_RULE_LINES provides the conditional logic and attribute mappings that drive those derivations.

From a Data Vault modeling perspective, the metadata's heuristic classification for this object is satellite-leaning. This reflects that AX_RULE_LINES functions primarily as a dependent descriptor table, carrying attributes about a parent rule entity rather than serving as an independent business hub or a pure associative link. Modeling practice would treat it as a satellite attached to the AX_RULES hub, keyed by the parent rule identifier.

Key Information Stored

AX_RULE_LINES contains 10 documented columns. The most significant are summarized below.

• RULE_ID – The foreign key referencing AX_RULES. This is the principal structural column and defines which rule set a given line belongs to. It is the join key to the parent rule definition.
• RECORD_ID – A record-level identifier for the line, serving as the surrogate or line-level key within the rule set. This distinguishes individual components within a single rule.
• TABLE_NAME – The name of the source table or entity to which the rule line applies. This identifies the data context evaluated by the rule component.
• COLUMN_NAME – The specific column or attribute being evaluated or mapped by the line. Together with TABLE_NAME, it defines the target of the rule logic.
• COLUMN_VALUE – The value, constant, or expression associated with the specified column, providing the condition or assignment used by the accounting engine.
• Audit columns – CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN capture standard EBS WHO-column auditing information, enabling traceability of rule line creation and modification.

The documented foreign key confirms RULE_ID as the business-relevant relationship to AX_RULES, while RECORD_ID typically plays the role of the line-level identifier. No alternate unique indexes are documented in the supplied metadata.

Common Use Cases and Queries

Typical use cases involve diagnosing accounting rule behavior, auditing rule configurations, and reporting on the conditions that drive derived accounting entries. A common query pattern joins AX_RULE_LINES to its parent rule set:

SELECT l.RULE_ID, l.RECORD_ID, l.TABLE_NAME, l.COLUMN_NAME, l.COLUMN_VALUE
FROM AX.AX_RULE_LINES l, AX.AX_RULES r
WHERE l.RULE_ID = r.RULE_ID
AND r.RULE_ID = :rule_id;

Extracting all lines referencing a particular source table or column:

SELECT RULE_ID, RECORD_ID, TABLE_NAME, COLUMN_NAME, COLUMN_VALUE
FROM AX.AX_RULE_LINES
WHERE TABLE_NAME = :table_name
AND COLUMN_NAME = :column_name;

These queries support impact analysis when rule sets are modified, troubleshooting of unexpected accounting entries, and configuration reconciliation between environments.

Related Objects

The most significant related object is the parent rule definition, joined through the documented foreign key.

• AX_RULES – Parent rule set table; joined via AX_RULE_LINES.RULE_ID = AX_RULES.RULE_ID. This is the primary relationship documented in the ETRM metadata.
• Other AX schema rule and mapping tables – Additional Global Accounting Engine configuration objects in the AX schema typically reference rule sets defined in AX_RULES and elaborated by AX_RULE_LINES, forming the broader rule engine configuration model.
• Global Accounting Engine processing routines and concurrent programs – These consume the rule definitions at runtime, indirectly depending on AX_RULE_LINES content.

Because the supplied metadata documents only the AX_RULES foreign key, additional relationships should be verified directly against the 12.1.1 and 12.2.2 AX schema before reliance.