Results for “ax_rules_v”

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

Overview

AX_RULES_V is a view within the AX - Global Accounting Engine (Global Accounting Engine) product of Oracle E-Business Suite. Per the documented ETRM metadata for release 12.2.2, the object is described as a "Duplicate of all rows of a subset of columns of table AX_RULES." This definition establishes the view as a simplified, read-oriented projection of its parent table rather than an independent data structure. It exposes only three identifying columns — APPLICATION_ID, RULE_ID, and RULE_NAME — drawn from the full column set of AX_RULES.

Because the Global Accounting Engine (AX) module was designed to convert subledger accounting events into general ledger entries in pre-11i and 11i-era architectures, the AX_RULES table and its views serve as the repository for rule definitions that drive that transformation. AX_RULES_V therefore functions as a lightweight reference object: consumers querying a rule by name or identifier need not touch the wider AX_RULES row, which may carry additional configuration attributes. In reporting and integration contexts, such views are typically used by Oracle Forms, concurrent programs, or downstream interfaces that require the rule list without the overhead or sensitivity of the full rule definition.

Underlying Base Objects

The view is defined over a single base object: the table AX_RULES. The view text is a straightforward SELECT DISTINCT projection over three columns, aliased to preserve their source names:

• APPLICATION_ID (from AX_RULES.APPLICATION_ID)
• RULE_ID (from AX_RULES.RULE_ID)
• RULE_NAME (from AX_RULES.RULE_NAME)

The DISTINCT keyword implies that AX_RULES may contain duplicate combinations of these three values, and the view guarantees a de-duplicated result set. The ETRM metadata lists "referenced base objects: none documented" and notes the view is "Not implemented in this database" in the captured environment; consequently, no formal foreign-key or dependency registry accompanies it. Any join to AX_RULES for additional attributes should be performed on the APPLICATION_ID and RULE_ID key pair, which uniquely identifies a rule within an application context.

Key Columns

• APPLICATION_ID — The identifier of the Oracle application that owns the rule. This column supports multi-application installations of the accounting engine, allowing rules to be partitioned by the originating application.
• RULE_ID — The internal sequence or surrogate identifier for the rule. It is the primary correlation key back to AX_RULES and to any dependent rule-detail or rule-line tables in the AX schema.
• RULE_NAME — The user-facing, descriptive name of the rule. The user's search term "rule_name" maps directly to this column, making it the principal column for human-readable lookups and for filtering in ad hoc queries.

Common Use Cases and Queries

Typical uses include resolving a rule name to its numeric identifier before invoking a concurrent program, populating a validation list of available rules, and auditing which rules exist for a given application. A representative query to locate a rule by name is:

• SELECT application_id, rule_id, rule_name FROM ax_rules_v WHERE rule_name = :p_rule_name;
• SELECT application_id, rule_id, rule_name FROM ax_rules_v WHERE application_id = :p_app_id ORDER BY rule_name;
• SELECT rule_name FROM ax_rules_v WHERE rule_id = :p_rule_id AND application_id = :p_app_id;

To retrieve attributes beyond the three exposed columns, join the view back to AX_RULES on APPLICATION_ID and RULE_ID. Note the ETRM caveat that the view is not implemented in all databases; deployments should verify its presence before relying on it in custom code.