Search Results location_profile_id

Overview

The HZ_LOCATION_PROFILES table is a core data object within the Oracle E-Business Suite (EBS) Trading Community Architecture (TCA) model, specifically under the Receivables (AR) product family. It functions as a historical and validation audit trail for address data. While the primary location details are stored in the HZ_LOCATIONS table, HZ_LOCATION_PROFILES captures a critical subset of these attributes over time. Its primary role is to maintain a record of changes and the outcomes of address validation processes for a given physical location, enabling businesses to track address evolution, ensure data quality, and support compliance by preserving a historical footprint of location information.

Key Information Stored

The table stores profile instances linked to a master location record. Key columns include the system-generated primary key, LOCATION_PROFILE_ID, which uniquely identifies each profile record. The foreign key, LOCATION_ID, ties the profile directly to its parent record in HZ_LOCATIONS. The table holds a snapshot of address attributes—such as address lines, city, state, postal code, and country—as they existed at a specific point in time. Crucially, it also stores metadata about changes and validations, including timestamps, the identity of the last updater, and statuses or codes resulting from automated or manual address validation services, indicating whether an address was confirmed, corrected, or flagged.

Common Use Cases and Queries

A primary use case is auditing address changes for a customer or site to understand historical mailing or shipping points. This is vital for dispute resolution or analyzing customer location trends. Another key use case is reporting on address validation efforts to measure data quality. Common SQL queries involve joining to HZ_LOCATIONS and party tables to get a full context.

• Retrieve Validation History for a Location: SELECT location_id, creation_date, last_update_date, last_updated_by, address_validation_status FROM hz_location_profiles WHERE location_id = <id> ORDER BY creation_date;
• Find Current vs. Historical Address: Join HZ_LOCATION_PROFILES (historical) with HZ_LOCATIONS (current) on LOCATION_ID to compare attributes.
• Data Quality Reporting: Aggregate queries on validation status columns to report counts of validated versus unvalidated addresses across the system.

Related Objects

The HZ_LOCATION_PROFILES table has a fundamental, documented relationship with the core TCA location table, forming a primary parent-child link.

• HZ_LOCATIONS: This is the primary parent table. The relationship is enforced by the foreign key where HZ_LOCATION_PROFILES.LOCATION_ID references HZ_LOCATIONS.LOCATION_ID. All location profiles are intrinsically tied to a single master location record. Queries almost always involve this join to retrieve the associated party or site information.

While not listed in the provided metadata, this table is also central to the TCA Data Quality (DQM) and Customer Data Hub (CDH) processes, interacting with various APIs and packages (e.g., HZ_LOCATION_PROFILE_V2PUB) used for creating, updating, and validating location profiles programmatically.