Results for “to_postal_code”

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

Overview

AR_LOCATION_RATES is an Oracle EBS view owned by the APPS schema and registered under the FND — Application Object Library product. In the 12.1.1 and 12.2.2 releases it presents a flattened, reporting-oriented projection of geographic location hierarchies derived from the Oracle Trading Community Architecture (TCA) geography model. Despite the AR_ prefix, which historically associates it with the Receivables module family, the view is not a physical table and contains no Receivables-specific taxation logic of its own; it is a compatibility construct that exposes postal-code-to-city relationships in the column layout expected by older location-rate consumers.

The view surfaces a conventional EBS audit and concurrency column set — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATED_BY, CREATION_DATE, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, and ATTRIBUTE_CATEGORY through ATTRIBUTE15 — allowing standard WHO column auditing, concurrent request tracing, and descriptive flexfield storage. Because it is a view rather than a table, no DML is permitted against it, and it should be treated strictly as a read-only data source for reporting, extracts, and integration queries.

Underlying Base Objects

The view is defined over two TCA base objects, both referenced through APPS synonyms: HZ_GEOGRAPHIES and HZ_RELATIONSHIPS. The join is driven by GEOGRAPHY_ID equal to RELATIONSHIPS.SUBJECT_ID, constrained by RELATIONSHIP_CODE = 'CHILD_OF'. This relationship code expresses the hierarchical link in which a postal code is a child of a city. The remaining predicates tighten the result set: GEOGRAPHY_TYPE must equal SUBJECT_TYPE, GEOGRAPHY_USE must be 'MASTER_REF', REL.OBJECT_TYPE must be 'CITY', and REL.SUBJECT_TYPE must be 'POSTAL_CODE'.

Consequently, one row is produced per qualifying postal-code-to-city relationship in the master reference geography hierarchy. Only effective-dated master reference geographies are returned, which excludes non-master or alternate geography uses maintained for other purposes within TCA.

Key Columns

• LOCATION_RATE_ID — mapped from GEOGRAPHY_ID; the primary identifier for the underlying geography record.
• LOCATION_SEGMENT_ID — mapped from REL.OBJECT_ID; identifies the related segment (the city object) in HZ_RELATIONSHIPS.
• FROM_POSTAL_CODE / TO_POSTAL_CODE — both sourced from GEOGRAPHY_NAME, reflecting the postal-code geography name in each direction.
• START_DATE / END_DATE — the effective date range of the geography record.
• ATTRIBUTE1 — mapped from GEOGRAPHY_CODE, with ATTRIBUTE2 through ATTRIBUTE15 passing through the corresponding HZ_GEOGRAPHIES attribute columns.
• OVERRIDE_STRUCTURE_ID, TAX_RATE, PROGRAM_UPDATE_DATE, OVERRIDE_RATE1 through OVERRIDE_RATE10 — exposed as literal NULLs. These columns exist solely to satisfy interface and report layouts inherited from the legacy AR_LOCATION_RATES structure.

Common Use Cases and Queries

Administrators and developers frequently locate this view when searching for override_rate1, because the column is published in the view definition yet never populated. Any query filtering or selecting OVERRIDE_RATE1 returns NULL for every row; tax and override rate data must instead be obtained from the Receivables tax setup tables (for example, AR_TAX_RATES_B and its related rate and jurisdiction tables), not from this view.

The practical purpose of AR_LOCATION_RATES is to resolve postal-code and city geography hierarchies for address validation, geography-based reporting, and legacy report compatibility. A representative query is:

• SELECT location_rate_id, from_postal_code, to_postal_code, location_segment_id, start_date, end_date FROM apps.ar_location_rates WHERE from_postal_code BETWEEN :low_value AND :high_value ORDER BY from_postal_code;

For district or region reporting, administrators join the returned LOCATION_SEGMENT_ID back to HZ_GEOGRAPHIES to obtain the parent city or region name. When debugging ETRM or tax-related documents in 12.2.2, note that the view's NULL override and tax rate columns are intentional placeholders; they carry no runtime data and should not be used to diagnose tax calculation results.