Results for “zip_end”

50+ results




Overview
Explore in AI Chat

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

Overview

HXC_TK_PAY_LOCATIONS is a reporting view owned by the APPS schema in Oracle E-Business Suite. It belongs to the HXC (Time and Labor Engine) product family and is documented in ETRM as a VALID view. Its stated purpose is to list work locations in a denormalized, human-readable format for use by the Time and Labor Engine and any downstream reporting or integration consumer that requires a flattened geographic address string.

The view does not store data. It is a read-only projection that assembles a single descriptive LOCATION string from United States geographic reference data, supplemented by discrete state, county, city, and ZIP attributes. Because the geographic reference tables are shared across Oracle HRMS and Payroll, the view provides a stable, reusable address construct that survives underlying table restructuring. On both 12.1.1 and 12.2.2 the view definition and column set are consistent, so custom reports, interfaces, and extracts built against it remain compatible across the upgrade boundary.

Underlying Base Objects

The view joins four synonym-based base objects, each resolving to the corresponding PAY_US_* table:

The join predicates are conformed on STATE_CODE, COUNTY_CODE, and CITY_CODE across the city, county, state, and ZIP objects. The WHERE clause restricts rows to states with STATE_CODE < 52 or STATE_CODE = 72, excluding certain non-contiguous or non-US territory codes. Output is ordered by CITY_NAME, STATE_NAME, COUNTY_NAME, and ZIP_START, producing a deterministic alphabetical listing grouped by city and county.

Key Columns

  • LOCATION — concatenated string of the form CITY_NAME || ', ' || STATE_NAME || ', ' || COUNTY_NAME || ' COUNTY, ' || ZIP_START. This is the primary display attribute.
  • STATE_ID — identifier used to associate the location with a state row; useful for filtering or joining to state-level views.
  • STATE — state name; the view also exposes STATE_ABBREV where a short code is required.
  • COUNTY — county name, presented without the trailing literal " COUNTY" that appears in the concatenated LOCATION.
  • CITY — city name.
  • ZIP — the ZIP_START value, the lower bound of the ZIP range for the city/county combination.
  • ZIP_END — the upper bound of the ZIP range, returned directly from PAY_US_ZIP_CODES.ZIP_END. A single city/county may map to a range, so ZIP and ZIP_END may differ.

Common Use Cases and Queries

The view is typically consumed by Time and Labor configuration reports, work-location list of values, geographic reference extracts, and third-party payroll interfaces that must resolve a city, county, or ZIP to a canonical location. Because ZIP_END is exposed directly, consumers searching for that attribute can enumerate ZIP ranges per city and county.

Retrieve the ZIP range for a given city:

  • SELECT city, county, state, zip, zip_end FROM hxc_tk_pay_locations WHERE city = 'DENVER' ORDER BY zip;

List locations whose ZIP range extends beyond a threshold:

  • SELECT location, zip, zip_end FROM hxc_tk_pay_locations WHERE zip_end > '90000' ORDER BY zip_end;

Use the view as a lookup for a Time and Labor work-location attribute by matching on STATE and CITY and selecting LOCATION for display. Note that the view returns read-only geographic reference data only; it contains no employee, assignment, or payroll processing attributes.