Search Results address_expiration_date




Overview
Explore in AI Chat

Overview

APPS.CSC_HZ_LOCATIONS_V is a reporting and integration view shipped in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It exposes a curated projection of the HZ_LOCATIONS entity, the Trading Community Architecture (TCA) table that stores the party and location addresses used across Receivables, Order Management, Service, and other modules. The view is owned by the APPS schema and is intended to provide a stable, simplified address interface for concurrent programs, Oracle Reports, Oracle Forms, and external integrations that should not query the base table directly.

Compared with HZ_LOCATIONS, the view narrows the column list to the attributes most commonly required for address display and processing, and it derives an additional ADDRESS column by concatenating ADDRESS1 through ADDRESS4 with semicolon delimiters. This formatting supports downstream reports and interfaces that expect a single free-form address line while preserving the discrete address elements.

Underlying Base Objects

The view is defined over a single referenced base object: HZ_LOCATIONS, accessed through a synonym in the APPS schema. The view definition is a straight SELECT from that table with no joins, unions, or aggregation, so row cardinality matches HZ_LOCATIONS exactly and no filtering is applied. The presence of last_update_date, last_updated_by, creation_date, created_by, and last_update_login indicates the standard WHO columns are carried through for audit and change-detection purposes. WH_UPDATE_DATE is also exposed, reflecting warehouse or data-merge update tracking used by TCA. Because the view is a thin wrapper, no additional indexing or tuning is introduced by the view itself; performance is governed entirely by HZ_LOCATIONS and its indexes.

Key Columns

  • LOCATION_ID — Primary identifier of the location record; the join key to HZ_PARTY_SITES and related TCA entities.
  • ADDRESS — Derived, delimited concatenation of ADDRESS1, ADDRESS2, ADDRESS3, and ADDRESS4. Null intermediate components are skipped so the semicolon separator appears only between populated elements.
  • ADDRESS1–ADDRESS4 — Individual address lines retained for structured formatting and validation.
  • CITY, STATE, PROVINCE, COUNTY, POSTAL_CODE, POSTAL_PLUS4_CODE, COUNTRY — Geographic components used for mailing, tax, and validation logic.
  • ADDRESS_STYLE — Indicates the formatting style applied to the address.
  • ADDRESS_EFFECTIVE_DATE — Date from which the address is valid.
  • ADDRESS_EXPIRATION_DATE — Date after which the address is no longer valid. This is the column most relevant to the searched term; it allows callers to distinguish active addresses from expired ones, a common requirement in customer master and party-site reporting.
  • ORIG_SYSTEM_REFERENCE — Identifier of the source system that originally created the location, supporting multi-source data consolidation.
  • CONTENT_SOURCE_TYPE — Classifies the origin of the address content.
  • Audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN, WH_UPDATE_DATE for change tracking and incremental extraction.

Common Use Cases and Queries

Typical scenarios include customer and supplier address reporting, data migration extracts, address validation feeds, and integrations that must refresh addresses incrementally. Because ADDRESS_EXPIRATION_DATE is exposed, a frequent pattern is to retrieve only currently effective addresses:

  • Party-site address listings that filter or partition records by ADDRESS_EXPIRATION_DATE to exclude superseded addresses.
  • Incremental extracts using LAST_UPDATE_DATE and WH_UPDATE_DATE for change data capture.
  • Displays in custom Forms or Reports requiring a single formatted ADDRESS string.

Sample query:

SELECT location_id, address, city, state, postal_code, country, address_effective_date, address_expiration_date FROM apps.csc_hz_locations_v WHERE (address_expiration_date IS NULL OR address_expiration_date >= SYSDATE) ORDER BY address_expiration_date;

For historical analysis, remove the expiration predicate or bound it with SYSDATE to identify expired addresses. In all cases the view returns one row per HZ_LOCATIONS record, so joins to HZ_PARTY_SITES on LOCATION_ID are required to associate addresses with specific parties and sites.