Results for “owner_type”

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

Overview

Within Oracle E-Business Suite, the view AHL_OWNER_DETAILS_V belongs to the AHL product family — Complex Maintenance Repair and Overhaul. It is owned by the APPS schema and carries a status of VALID. The view exposes a unified, reporting-oriented query that resolves the set of valid owners that may be associated with a Unit Configuration in the AHL module.

The defining purpose of the view, as stated in its documentation, is to store the query used to retrieve valid owners for a Unit Configuration. Rather than maintaining owner data in a dedicated table, the view composes owner records dynamically from two independent registries: trading community parties and purchasing vendors. The result is a single query surface that presents organizations, persons, and vendors as candidate owners, each with a normalized identifier, number, name, type, and address. Because it consolidates what would otherwise be multiple lookups, the view serves as a convenient integration and reporting endpoint for any process that needs to enumerate ownership candidates for AHL unit configurations.

Underlying Base Objects

The view is defined as a UNION ALL of two sources:

• HZ_PARTIES — referenced through a synonym. This branch yields parties whose status is not 'I' (inactive) and whose party type is either ORGANIZATION or PERSON. The branch is tagged with the literal 'PARTY' as the PARTY_TYPE discriminator.
• PO_VENDORS — referenced as a view. This branch supplies vendor identifiers, numbers, names, and lookup codes from the purchasing schema, and is tagged with the literal 'VENDOR' as the PARTY_TYPE discriminator. Its address column is returned as NULL.

The use of UNION ALL preserves all rows from both branches without deduplication. Because the two branches are drawn from distinct registries, an entity that exists both as a party and as a vendor may appear under each identity. The address composition logic applies only to the HZ_PARTIES branch, concatenating address lines and geographic attributes with semicolon delimiters while omitting null components.

Key Columns

• OWNER_ID — the owner identifier; sourced from PARTY_ID in the party branch and VENDOR_ID in the vendor branch.
• OWNER_NUMBER — the owner's reference number; PARTY_NUMBER for parties and SEGMENT1 for vendors.
• OWNER_NAME — the display name; PARTY_NAME for parties and VENDOR_NAME for vendors.
• OWNER_TYPE — the classification of the owner; PARTY_TYPE for parties and VENDOR_TYPE_LOOKUP_CODE for vendors.
• PARTY_TYPE — the source discriminator, returning either 'PARTY' or 'VENDOR'. This is the primary column for distinguishing the origin of a row.
• ADDRESS — a semicolon-delimited concatenation of address lines, city, postal code, state, province, and country, populated only for party rows and returned as NULL for vendor rows.

Common Use Cases and Queries

The view is typically consumed to populate owner selection lists in AHL unit configuration screens, to validate owner references during data migration, and to support reporting on ownership across parties and vendors.

To list all candidate owners in name order:

SELECT owner_id, owner_number, owner_name, party_type
FROM   apps.ahl_owner_details_v
ORDER  BY owner_name;

To return only vendors, or only trading community parties:

SELECT owner_id, owner_number, owner_name
FROM   apps.ahl_owner_details_v
WHERE  party_type = 'VENDOR';

To search for a specific owner by number:

SELECT owner_id, owner_name, party_type, address
FROM   apps.ahl_owner_details_v
WHERE  owner_number = :p_owner_number;