Results for “ar_ta_rules”

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

Overview

AR_TA_RULES is a reporting view in the Oracle E-Business Suite Receivables (AR) module, documented in ETRM as a SINGLE_ORG view. Its purpose is to expose the Tax Authority rules configuration maintained by Receivables and related tax processing functionality, while restricting the rows returned to the operating unit context of the current session. In Oracle EBS 12.1.1 and 12.2.2, multi-organization architecture stores setup data in an "_ALL" table and exposes a "SINGLE_ORG" view whose WHERE clause filters on ORG_ID using the USERENV('CLIENT_INFO') mechanism. AR_TA_RULES is therefore the org-secured presentation layer over the underlying AR_TA_RULES_ALL table, and is the object that application code, reports, and integrations query when they need to work within the boundaries of the active organization rather than across all operating units.

The view's columns include the standard EBS audit and descriptive column set (Who columns, ATTRIBUTE1 through ATTRIBUTE15, ATTRIBUTE_CATEGORY) plus domain-specific fields such as RULE_TYPE, SHORT_NAME, DESCRIPTION, PROCEDURE_NAME, ACTIVE_FLAG, and ORG_ID. Because the view performs no joins and simply re-projects and filters the base table, it is a lightweight, low-overhead access path suitable for both online queries and batch reporting.

Underlying Base Objects

According to the ETRM metadata, the only documented underlying object for AR_TA_RULES is AR_TA_RULES_ALL. The view definition is a straightforward SELECT of the base table's columns with a restricting predicate on ORG_ID. No joins, aggregations, or additional referenced objects are documented. The filter uses the classic EBS multi-org idiom: the client's organization context is read from USERENV('CLIENT_INFO'), the first character is inspected to detect a leading space (an unset or invalid context), and the numeric organization identifier is compared to ORG_ID. Rows whose ORG_ID is null, and sessions whose client information cannot be resolved, both collapse to the sentinel value -99, ensuring that data outside the current operating unit is not exposed.

This design means AR_TA_RULES cannot return data for more than one organization in a single session, and it must be preceded by the correct initialization of the client context (typically performed by the FND_GLOBAL / multi-org session setup). The metadata explicitly notes that the view is documented but that base objects beyond AR_TA_RULES_ALL are not listed, and that the object is marked as not implemented in the source database from which the excerpt was taken.

Key Columns

• RULE_ID – Primary identifier for the tax authority rule record.
• RULE_TYPE – Classifies the rule; this is the attribute most frequently used to discriminate between rule categories, and is the term most commonly used when searching for this view.
• SHORT_NAME – Concise, user-facing name for the rule.
• DESCRIPTION – Free-text explanation of the rule's purpose or behavior.
• PROCEDURE_NAME – Name of the stored procedure or program associated with the rule's execution logic.
• ACTIVE_FLAG – Indicates whether the rule is currently enabled.
• ATTRIBUTE_CATEGORY, ATTRIBUTE1–ATTRIBUTE15 – Descriptive flexfield columns for extensible, customer-defined attributes.
• ORG_ID – Operating unit that owns the rule; the column driving the single-org filter.
• Audit columns – LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATION_DATE, CREATED_BY.

Common Use Cases and Queries

Typical uses include validating which tax authority rules are active for the current operating unit, joining rule definitions to transaction tax lines, and driving custom reports or integrations that must respect org-level security.

A representative query returning all active rules in the current organization:

• SELECT rule_id, rule_type, short_name, procedure_name FROM ar_ta_rules WHERE active_flag = 'Y' ORDER BY rule_type, short_name;

Filtering by a specific rule type, the most common lookup pattern:

• SELECT rule_id, short_name, description FROM ar_ta_rules WHERE rule_type = :p_rule_type AND NVL(active_flag,'N') = 'Y';

Because AR_TA_RULES is org-secured, no explicit ORG_ID predicate is required; the client context must already be set. For cross-organization analysis, the base table AR_TA_RULES_ALL may be queried directly where privileges permit, but standard Receivables reporting should use AR_TA_RULES to preserve operating unit boundaries.