Search Results tax_reference




Overview

XTR_PARTY_DEFAULTS_V is a view owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2, delivered as part of the XTR (Treasury) product. The view exposes the default configuration records that govern how treasury deals are set up for a given party (counterparty or internal party). Each row represents a combination of party, deal type, deal subtype, product type, and default type that determines the standard settlement, tax, and brokerage treatment applied when treasury transactions are created for that party.

Because it is a view rather than a base table, XTR_PARTY_DEFAULTS_V is intended primarily for read-only reporting, data extraction, and integration. External systems, custom reports, and interfaces that need to retrieve a party's default tax, brokerage, or settlement references can query the view without touching the underlying base table directly. The view is particularly relevant to searches involving tax_reference, since it exposes both TAX_REFERENCE and INCOME_TAX_REFERENCE columns. The object carries a status of VALID and its definition is a straightforward projection over a single synonym.

Underlying Base Objects

The documented view text selects from a single object: XTR_PARTY_DEFAULTS. In the APPS schema this object is registered as a SYNONYM, which in turn resolves to the XTR base table holding the party default definitions. There is no join, aggregation, or filtering in the view definition; it is a flat column projection. The view does not add calculated columns or rename data — every column it exposes corresponds directly to a column on XTR_PARTY_DEFAULTS.

Because the relationship is one-to-one with the base synonym, query performance and row counts through the view mirror those of the underlying table. Any DML restrictions applicable to the base table also apply to the view; it is intended for query access, not maintenance. When the underlying table structure changes between patch levels, the view definition is the only interface that custom code should depend on, reducing the impact of base object evolution.

Key Columns

The view exposes the full attribute set of the underlying record. The most operationally significant columns include:

Common Use Cases and Queries

Typical use cases include retrieving the tax reference configured for a party before creating a deal, auditing default setup across parties, and feeding settlement or brokerage references into an outbound interface. A representative query to locate the tax references defined for a party is:

  • SELECT party_code, deal_type, deal_subtype, product_type, tax_reference, income_tax_reference, tax_category FROM xtr_party_defaults_v WHERE party_code = :p_party_code;
  • SELECT party_code, default_type, brokerage_reference, brokerage_category FROM xtr_party_defaults_v WHERE tax_reference IS NOT NULL;
  • SELECT transaction_number, interest_settled_by, principal_settled_by, freq_interest_settled FROM xtr_party_defaults_v WHERE product_type = :p_product_type;

These queries support reconciliation, setup validation, and integration extracts while insulating custom code from the underlying XTR_PARTY_DEFAULTS table structure.