Results for “postal_plus4_code”

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

Overview

CSC_HZ_LOCATIONS_V is a read-only view owned by the APPS schema in Oracle E-Business Suite, registered under the CSC - Customer Care product family. Its documented purpose is to expose location details sourced from the Trading Community Architecture (TCA) location repository. Because Customer Care functionality depends heavily on accurate party-site and address information, this view delivers a simplified projection of the underlying location table for use in forms, concurrent programs, and reporting layers.

The view is documented as VALID in both ETRM 12.1.1 and 12.2.2. It is not a denormalized or aggregated object; it is a thin wrapper that selects a defined subset of columns from the base location entity, making it suitable where a stable interface is required without exposing the full breadth of the underlying table.

Underlying Base Objects

The view is defined over HZ_LOCATIONS, referenced in the metadata as HZ_LOCATIONS (SYNONYM), the public synonym resolving to the TCA master location table. The transformation is minimal and consists of two documented behaviors:

• Direct pass-through of all listed columns, including LOCATION_ID, COUNTRY, ADDRESS1 through ADDRESS4, CITY, POSTAL_CODE, STATE, PROVINCE, COUNTY, and ADDRESS_STYLE.
• A single concatenation that derives an ADDRESS column by joining ADDRESS1, ADDRESS2, ADDRESS3, and ADDRESS4 with semicolon delimiters, using nested DECODE calls that suppress the delimiter when a component address line is null. This produces a compact single-field representation of the street address.

No joins, filters, or WHERE predicates are applied. Consequently, row counts and key values in the view match HZ_LOCATIONS exactly, and the view inherits the base table's concurrency and indexing characteristics.

Key Columns

The ADDRESS_STYLE column is of particular interest, as it is the term most frequently associated with this object. It identifies the formatting convention applied to an address record within TCA, governing how address elements are rendered or validated for a given country or geography. Values typically correspond to style codes defined in the address style setup used by TCA and geography validation.

• LOCATION_ID — Primary identifier of the location record; the join key to party sites, customer accounts, and other TCA entities.
• ADDRESS — Derived, semicolon-delimited concatenation of the four address lines.
• ADDRESS1–ADDRESS4 — Individual address line components retained in native form.
• CITY, STATE, PROVINCE, COUNTY, POSTAL_CODE, POSTAL_PLUS4_CODE — Standard geographical attributes.
• COUNTRY — Country code for the location.
• ADDRESS_EFFECTIVE_DATE / ADDRESS_EXPIRATION_DATE — Validity window for the address record.
• ORIG_SYSTEM_REFERENCE and CONTENT_SOURCE_TYPE — Identify the source system and content origin, supporting data-integration and audit tracing.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, and WH_UPDATE_DATE.

Common Use Cases and Queries

The view is commonly used to retrieve formatted addresses for customers, to inspect address style assignments, and to reconcile location data imported from external systems via ORIG_SYSTEM_REFERENCE.

• Locate locations by address style, for example:

  SELECT location_id, address, city, country, address_style
  FROM   csc_hz_locations_v
  WHERE  address_style IS NOT NULL;

• Retrieve a formatted address for a known location:

  SELECT location_id, address, postal_code
  FROM   csc_hz_locations_v
  WHERE  location_id = :p_location_id;

• Trace externally sourced locations:

  SELECT location_id, orig_system_reference, content_source_type, address_style
  FROM   csc_hz_locations_v
  WHERE  orig_system_reference IS NOT NULL;

Because the view performs no filtering, queries should always constrain on LOCATION_ID or another indexed attribute to avoid full scans of the underlying TCA table, and should account for effective and expiration dates when current-address accuracy is required.