Search Results override_rate1

Overview

The AR_LOCATION_RATES view is a foundational data object within Oracle E-Business Suite (EBS) Release 12.1.1 and 12.2.2, owned by the APPS schema. While its name suggests a potential link to tax or freight rates based on location, the documented view definition reveals its primary role is to expose hierarchical relationships between postal codes and cities from the Trading Community Architecture (TCA) model. It serves as a standardized interface for applications to query postal code ranges associated with specific city locations. This view is part of the Application Object Library (FND) module, indicating its use as a shared, cross-module resource for location data, rather than being specific to the Accounts Receivable (AR) module as the prefix might imply.

Key Information Stored

The view's columns can be categorized into several key groups. The primary location relationship data includes LOCATION_RATE_ID (the unique ID of the postal code geography), LOCATION_SEGMENT_ID (the ID of the parent city object), and the FROM_POSTAL_CODE and TO_POSTAL_CODE (both populated from GEOGRAPHY_NAME). Temporal validity is managed via START_DATE and END_DATE. Standard EBS audit columns are present: CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN. The view also includes a set of fifteen descriptive ATTRIBUTE columns, with ATTRIBUTE1 populated by the GEOGRAPHY_CODE. Notably, several columns such as TAX_RATE, OVERRIDE_STRUCTURE_ID, and the OVERRIDE_RATE1 through OVERRIDE_RATE10 columns are hard-coded to NULL in the current definition, suggesting this view may serve as a template or legacy structure for extended functionality.

Common Use Cases and Queries

The primary use case is retrieving the list of postal codes that are valid children of a given city within the TCA hierarchy. This is essential for data validation, address cleansing, and reporting processes that require geographic grouping. A common query pattern involves joining this view to other TCA-based tables, such as HZ_LOCATIONS or party sites, to enrich transaction data with location details. For example, to find all postal code ranges for a specific city, one would query: SELECT from_postal_code, to_postal_code FROM apps.ar_location_rates WHERE location_segment_id = &city_id;. For reporting, the view can be used to aggregate customer or transaction counts by city based on postal code ranges. The presence of start and end dates also supports queries for historical location hierarchies.

Related Objects

The view's definition is directly and exclusively built upon two core TCA tables, establishing clear relationships.

• HZ_GEOGRAPHIES: The view joins to this table on GEO.GEOGRAPHY_ID = REL.SUBJECT_ID to obtain the details of the postal code geography (GEOGRAPHY_TYPE = 'POSTAL_CODE'). This is the source for most descriptive and audit columns in the view.
• HZ_RELATIONSHIPS: The view joins to this table to establish the hierarchical link. The join condition filters for relationships where the subject (child) is a 'POSTAL_CODE' and the object (parent) is a 'CITY', with a RELATIONSHIP_CODE of 'CHILD_OF'. This defines the core parent-child relationship the view exposes.

Given its FND module classification, AR_LOCATION_RATES is likely referenced by various standard reports, interfaces, and possibly other views across financial, distribution, and CRM modules that require postal-code-to-city mappings.