Results for “actual_content_source”

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

Overview

HZ_LOCATION_PROFILES is a table owned by the AR schema in Oracle E-Business Suite, documented as part of the Receivables (AR) product family and referenced extensively by the Oracle Trading Community Architecture (TCA) model. Its stated purpose is to store information — including a history of changes and address validations — for a subset of attributes drawn from HZ_LOCATIONS. Rather than duplicating the full location record, the table captures dated profiles that describe how a particular location's address attributes were validated and how those values changed over time.

In Data Vault modeling terms, the mined relationship structure classifies HZ_LOCATION_PROFILES as satellite-leaning. This reflects its single foreign key dependency on HZ_LOCATIONS, its effective-dated columns, and its descriptive validation attributes — characteristics typical of a satellite attached to a parent hub or link rather than a standalone hub or associative link.

Key Information Stored

The table contains 27 columns. The most significant are described below.

• LOCATION_PROFILE_ID — the surrogate primary key, enforced by HZ_LOCATION_PROFILES_PK and also a unique-index candidate via HZ_LOCATION_PROFILES_U1. This is the column most commonly referenced by the search term location_profile_id.
• LOCATION_ID — the foreign key to HZ_LOCATIONS, identifying the parent location whose attributes are profiled.
• ACTUAL_CONTENT_SOURCE — indicates the origin of the profiled attribute values.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — define the date range during which the profile row is valid, supporting historical tracking.
• VALIDATION_STATUS_CODE / VALIDATION_SST_FLAG / DATE_VALIDATED — capture the outcome, classification, and timestamp of address validation processing.
• ADDRESS1–ADDRESS4, CITY, COUNTY, POSTAL_CODE, PROV_STATE_ADMIN_CODE, COUNTRY — the address attribute subset replicated for profile and validation purposes.
• OBJECT_VERSION_NUMBER — optimistic locking column for concurrent updates.
• Audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATION_DATE, CREATED_BY, and the PROGRAM/REQUEST_ID columns record who changed the row and which concurrent program performed the change.

Common Use Cases and Queries

Typical use cases include retrieving the current validated address profile for a location, auditing historical validation results, and identifying locations whose validation has expired or failed. A representative query for the active profile of a given location is:

• SELECT location_profile_id, location_id, validation_status_code, date_validated FROM hz_location_profiles WHERE location_id = :p_location_id AND SYSDATE BETWEEN effective_start_date AND NVL(effective_end_date, SYSDATE);
• Reporting failed validations: SELECT COUNT(*) FROM hz_location_profiles WHERE validation_status_code = 'FAILED';
• Joining to the parent location for enrichment: SELECT l.location_id, p.validation_status_code FROM hz_locations l, hz_location_profiles p WHERE l.location_id = p.location_id;

Related Objects

• HZ_LOCATIONS — the parent table, joined via HZ_LOCATION_PROFILES.LOCATION_ID = HZ_LOCATIONS.LOCATION_ID.
• HZ_LOCATION_PROFILES_PK / HZ_LOCATION_PROFILES_U1 — primary and unique constraints on LOCATION_PROFILE_ID.
• TCA APIs such as HZ_LOCATION_V2PUB and the Location Profile public APIs, which read and write profile rows during address validation.
• AR customer and party views that resolve party site addresses through HZ_LOCATIONS and this profile table.