Search Results owner_number




Overview
Explore in AI Chat

Overview

APPS.AHL_OWNER_DETAILS_V is a reporting and integration view in Oracle E-Business Suite (12.1.1 and 12.2.2) that presents a consolidated list of "owners" available to the Asset Lifecycle / enterprise asset functionality. Its role is to expose a single, uniform source of owner candidates drawn from two distinct populations in the EBS data model: trading partners (parties) and suppliers (vendors). Because it unifies these two sources behind a common column set, the view allows upstream forms, lookups, and reports to query a single object rather than performing their own unions across HZ_PARTIES and PO_VENDORS.

The presence of the OWNER_NUMBER column is significant because it is the alias applied to two different source attributes: PARTY_NUMBER from HZ_PARTIES and SEGMENT1 from PO_VENDORS. Users searching on "owner_number" are typically looking for the human-readable identifier by which an owner is recognized — the party number for a party, or the supplier number for a vendor.

Underlying Base Objects

The view is owned by APPS and is defined over two documented base objects: HZ_PARTIES (referenced through a SYNONYM) and PO_VENDORS (referenced as a VIEW). The two branches are combined with UNION ALL, so no deduplication occurs; the same real-world entity could theoretically appear twice if it exists both as a party and as a vendor.

The first branch selects from HZ_PARTIES, filtered to exclude inactive records (STATUS <> 'I') and restricted to party types ORGANIZATION and PERSON. The second branch selects from PO_VENDORS without a status filter. A literal discriminator, PARTY_TYPE, is hard-coded to 'PARTY' in the first branch and 'VENDOR' in the second, allowing consumers to identify the provenance of each row.

Key Columns

  • OWNER_ID — The primary identifier of the owner. Maps to PARTY_ID for party rows and VENDOR_ID for vendor rows.
  • OWNER_NUMBER — The business-facing owner number. Maps to PARTY_NUMBER (parties) and SEGMENT1 (vendors).
  • OWNER_NAME — The descriptive name. Maps to PARTY_NAME or VENDOR_NAME.
  • OWNER_TYPE — The owner classification. Maps to PARTY_TYPE for parties and VENDOR_TYPE_LOOKUP_CODE for vendors. Note this column name is distinct from the discriminator below.
  • PARTY_TYPE — A literal source discriminator: 'PARTY' or 'VENDOR'.
  • ADDRESS — A concatenated address string built from ADDRESS1 through ADDRESS4, CITY, POSTAL_CODE, STATE, PROVINCE, and COUNTRY, semicolon-delimited. It is populated only for party rows; vendor rows return NULL.

Common Use Cases and Queries

The view is typically used to populate owner selection lists and to resolve an owner number to its identifier and name. A straightforward lookup by number demonstrates its core purpose:

  • SELECT owner_id, owner_number, owner_name, party_type FROM apps.ahl_owner_details_v WHERE owner_number = :p_number;
  • SELECT owner_id, owner_name FROM apps.ahl_owner_details_v WHERE UPPER(owner_name) LIKE UPPER('%'||:p_name||'%') ORDER BY owner_name;
  • SELECT party_type, COUNT(*) FROM apps.ahl_owner_details_v GROUP BY party_type; — useful for confirming the distribution of party versus vendor owners.

Because OWNER_ID is not globally unique across the two branches in a purely theoretical sense, queries that join back to source tables should include the PARTY_TYPE discriminator to ensure the correct base object is referenced. The address column should be treated as party-specific, and consumers requiring vendor addresses must retrieve them separately from the supplier tables. This view is therefore best regarded as an owner enumeration and identification aid rather than a complete master record.