Search Results ap_tax_recvry_rules_all




Overview
Explore in AI Chat

Overview

The AP_TAX_RECVRY_RULES_ALL table is a historical data object within Oracle E-Business Suite Release 12.1.1 and 12.2.2, specifically for the Payables (AP) module. Its primary documented role was to store master definitions for tax recovery rules, which are business rules governing how tax amounts can be reclaimed or recovered from tax authorities, a common requirement in jurisdictions with value-added tax (VAT) or goods and services tax (GST) regimes. However, as per the official ETRM documentation, this table is explicitly marked as "No longer used" in the provided releases. This indicates that while the table structure may still exist in the database schema for backward compatibility, its functional logic has been superseded by other components within the Oracle E-Business Suite tax engine.

Key Information Stored

Based on the documented primary and unique keys, the table was designed to store rule definitions identifiable by a system-generated identifier and a unique name. The key columns include:

  • RULE_ID: The primary key column, a unique numeric identifier for each tax recovery rule.
  • NAME: A unique alphanumeric name for the rule, serving as a user-friendly identifier (enforced by the AP_TAX_RECVRY_RULES_UK1 unique key).

While other columns are not detailed in the provided excerpt, a typical structure for such a rule table could have included columns for effective dates, description, recovery type, and other rule attributes necessary for calculating recoverable tax amounts on invoices.

Common Use Cases and Queries

Given its "No longer used" status, direct operational use cases or transactional reporting against this table are obsolete. The primary contemporary use case is for historical analysis or data cleanup activities. For instance, a technical consultant might query to identify if any legacy data persists or to understand old configurations before a migration. A sample diagnostic query would be:

SELECT rule_id, name FROM ap_tax_recvry_rules_all WHERE SYSDATE BETWEEN start_date_active AND NVL(end_date_active, SYSDATE);

This would check for any rules that are still marked as active. Another common pattern involves joining to its related tables, like AP_TAX_CODES_ALL, to audit historical linkages: SELECT tax_name, trx.name AS recovery_rule_name FROM ap_tax_codes_all tax, ap_tax_recvry_rules_all trx WHERE tax.tax_recovery_rule_id = trx.rule_id(+);

Related Objects

The ETRM documentation specifies two key foreign key relationships, indicating how this table was historically integrated into the application's data model:

  • AP_TAX_CODES_ALL: The TAX_RECOVERY_RULE_ID column in this table references AP_TAX_RECVRY_RULES_ALL.RULE_ID. This linked a tax code definition to a specific recovery rule.
  • AP_TAX_RECVRY_RATES_ALL: The RULE_ID column in this table references AP_TAX_RECVRY_RULES_ALL.RULE_ID. This allowed multiple recovery rates (likely based on time or product) to be associated with a single master rule.

These relationships confirm the table's role as a parent or master table for tax recovery configuration, with child tables storing specific rates and tax code assignments.