Search Results xtr_tax_brokerage_setup




Overview

XTR.XTR_TAX_BROKERAGE_SETUP is a Treasury (XTR) module configuration table that stores tax and brokerage schedule information used during deal processing. It defines the deduction rules — including tax and brokerage rates, calculation logic, payment destinations, and rounding behavior — that the Treasury engine applies when computing charges against financial deals. In Oracle EBS 12.1.1 and 12.2.2, the table is native to the XTR schema and remains VALID in the data dictionary, indicating it is an actively maintained setup entity rather than a legacy artifact.

From a Data Vault modeling perspective, the mined foreign key structure classifies this object as satellite-leaning. This is a heuristic suggestion rather than a physical design fact: the table records descriptive, attribute-rich configuration details tied to a deduction reference, with limited outgoing referential dependencies, which is characteristic of a satellite entity rather than a hub or a link.

Key Information Stored

The table carries 17 documented columns. The most significant business attributes include:

  • REFERENCE_CODE — the primary business identifier for a tax/brokerage setup record; also the sole column in unique index XTR_TAX_BROKERAGE_SETUP_U1, making it the leading business-key candidate.
  • DEDUCTION_TYPE — the classification of the deduction (for example, tax versus brokerage); combined with REFERENCE_CODE it forms the composite primary key XTR_TAX_BROKERAGE_SETUP_PK and unique index _UK1.
  • DEAL_TYPE and CALC_TYPE — determine which deal categories and calculation methods the setup applies to; these are the columns participating in the foreign key to XTR_DEDUCTION_CALCS.
  • RATE_GROUP — links the schedule to the rate group that supplies the applicable percentage or amount.
  • PAYEE — the party to whom the tax or brokerage amount is remitted.
  • DESCRIPTION — free-text identification of the schedule.
  • AUTHORISED — status flag governing whether the setup is active for processing.
  • NOMINAL_ANNUAL_TAX_BREAK — threshold or nominal annual value used in annual tax break determinations.
  • TAX_ROUNDING_RULE and TAX_ROUNDING_PRECISION — control how computed tax amounts are rounded and to what precision.
  • TAX_SETTLE_METHOD — the settlement method applied to the tax amount.
  • AUDIT_INDICATOR — flag controlling audit of changes to the record.
  • CREATED_BY, CREATED_ON, UPDATED_BY, UPDATED_ON — standard Oracle EBS audit/WHO columns capturing record creation and last modification.

The surrogate primary key is XTR_TAX_BROKERAGE_SETUP_PK, a composite of REFERENCE_CODE and DEDUCTION_TYPE. Business-key candidates are documented through the unique indexes: _U1 on REFERENCE_CODE and _UK1 on DEDUCTION_TYPE, RATE_GROUP, PAYEE, DEAL_TYPE, and CALC_TYPE.

Common Use Cases and Queries

Typical usage centers on setup maintenance, deal simulation, and reconciliation reporting. Administrators query this table to verify which deduction schedules are active for a given deal type, and developers use it to trace how a specific tax or brokerage amount was derived during deal accounting.

  • Listing active schedules by deal type: SELECT reference_code, deduction_type, rate_group, payee FROM xtr_tax_brokerage_setup WHERE deal_type = :p_deal_type AND authorised = 'Y';
  • Auditing rounding behavior: SELECT reference_code, tax_rounding_rule, tax_rounding_precision, tax_settle_method FROM xtr_tax_brokerage_setup WHERE deduction_type = :p_type;
  • Joining to the calculation definition to validate calc logic: SELECT s.reference_code, c.calc_type FROM xtr_tax_brokerage_setup s, xtr_deduction_calcs c WHERE s.deal_type = c.deal_type AND s.calc_type = c.calc_type;
  • Detecting stale or duplicate business keys using the unique index columns.

Related Objects

The principal related object is XTR_DEDUCTION_CALCS, joined via XTR_TAX_BROKERAGE_SETUP.DEAL_TYPE and XTR_TAX_BROKERAGE_SETUP.CALC_TYPE. This foreign key ties the tax/brokerage schedule to the underlying deduction calculation definition. Additional significant dependencies include the Rate Group and Payee configuration objects referenced by RATE_GROUP and PAYEE, the Treasury deal tables that consume these schedules during deduction processing, and the standard FND audit and concurrency objects that populate the WHO columns and AUTHORISED status. Together these form the surrounding setup and transaction constellation within the XTR schema.