Results for “ar_postal_code_ranges_v”

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

Overview

The AR_POSTAL_CODE_RANGES_V view is a public Oracle E-Business Suite database object owned by the APPS schema and classified under the Receivables (AR) product family. According to the documented ETRM metadata, this view is designated as Release 115 Only, meaning its intended functional scope belongs to an earlier generation of the Receivables application rather than the current 12.1.1 or 12.2.2 code lines. Its status is listed as VALID, indicating that the compiled object remains present and functional in the database dictionary, even where the surrounding business functionality has been superseded.

The view is designed to expose active postal code range definitions used for tax determination. It filters the underlying location rate data so that only rows whose effective date window encompasses the current system date (SYSDATE BETWEEN START_DATE AND END_DATE) are returned. This date-sensitive filter makes the view a convenient source of "currently effective" postal code ranges for reporting, reconciliation, and integration purposes, without requiring the caller to reimplement the effective-dating logic. Because it is a view rather than a table, it carries no storage of its own and reflects the state of its base object at query time.

Underlying Base Objects

The view is defined exclusively over a single documented base object: AR_LOCATION_RATES, which is itself identified in the metadata as a view. The dependency chain is therefore a view-on-view construct, and any performance or data-freshness characteristics of AR_POSTAL_CODE_RANGES_V are inherited directly from AR_LOCATION_RATES.

The defining query selects from AR_LOCATION_RATES with a restrictive predicate on the effective date range (START_DATE and END_DATE). It performs no joins and no aggregations, so the cardinality of the result set is a subset of the rows in AR_LOCATION_RATES. The view also performs column aliasing: the base column ATTRIBUTE1 is republished as SALES_TAX_GEOCODE, providing a more descriptive name for consumers. Administrators inspecting dependencies in the data dictionary will see AR_LOCATION_RATES as the sole referenced object, and any change to the structure or contents of that underlying view propagates immediately to AR_POSTAL_CODE_RANGES_V.

Key Columns

• LOCATION_RATE_ID — The primary identifier for the location rate record, carried through unchanged from the base object and useful for joining back to AR_LOCATION_RATES.
• FROM_POSTAL_CODE — The lower bound of the postal code range covered by the record.
• TO_POSTAL_CODE — The upper bound of the postal code range. Together with FROM_POSTAL_CODE, it defines the interval of postal codes to which the associated tax rate applies.
• LOCATION_SEGMENT_ID — The identifier of the location segment (for example, a geography or tax jurisdiction component) associated with the range.
• SALES_TAX_GEOCODE — An alias for the base column ATTRIBUTE1, representing the sales tax geocode assigned to the postal code range.
• TAX_RATE — The tax rate applicable to the postal code range for the current effective period.

Common Use Cases and Queries

Because the view applies effective-date filtering automatically, it is most commonly used where a report or interface must resolve the tax rate or geocode in force today for a given postal code. Typical scenarios include tax rate verification during Receivables transaction entry, reconciliation of tax setup against external tax engines, and ad hoc analysis of postal code coverage.

The simplest query lists all currently effective ranges:

• SELECT location_rate_id, from_postal_code, to_postal_code, location_segment_id, sales_tax_geocode, tax_rate FROM apps.ar_postal_code_ranges_v;
• SELECT from_postal_code, to_postal_code, tax_rate FROM apps.ar_postal_code_ranges_v WHERE tax_rate IS NOT NULL ORDER BY from_postal_code;

To resolve a specific postal code, a BETWEEN predicate on the range columns can be applied:

• SELECT tax_rate, sales_tax_geocode FROM apps.ar_postal_code_ranges_v WHERE :postal_code BETWEEN from_postal_code AND to_postal_code;

Given the Release 115 Only designation, implementations on 12.1.1 or 12.2.2 should confirm whether this view is still referenced by active customization or integration code before relying on it, and should plan migration to the supported tax configuration objects where applicable.