Search Results application_owner_name




Overview
Explore in AI Chat

Overview

AMW_HIERARCHY_ENTITIES_V is a read-only database view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the AMW — Internal Controls Manager product. Its documented description states that it "lists process details from amw_process and workflow tables." In practice the view exposes a flattened, reporting-friendly projection of internal control processes, including the process hierarchy revision identifiers, descriptive display names sourced from a workflow translation table, classification flags, certification and approval status attributes, risk, control, and organization counters, and resolved party names for the several ownership roles defined against each process. Because the underlying AMW tables are not exposed through standard Oracle EBS forms in a denormalized form, this view serves as the primary reporting and integration access point for process-level governance data.

The view is especially relevant to consumers who need to resolve ownership attributes such as APPLICATION_OWNER_NAME. The user keyword "application_owner_name" maps directly to a column exposed by this view, which is resolved from the HZ_PARTIES table rather than stored as a free-text attribute on the process record.

Underlying Base Objects

The view text draws on AMW_PROCESS (aliased AMWP) as its driving table. It joins to a workflow display table (WA_TL, aliased WA_TL) to obtain PROCESS_DISPLAY_NAME, and to HZ_PARTIES three times — HZP1, HZP2, and HZP3 — to resolve PROCESS_OWNER_NAME, APPLICATION_OWNER_NAME, and FINANCE_OWNER_NAME respectively. Lookup meanings are resolved through calls to AMW_UTILITY_PVT.GET_LOOKUP_MEANING for the AMW_CERTIFICATION_STATUS, AMW_PROCESS_APPROVAL_STATUS, and AMW_PROCESS_CATEGORY lookup types.

The documented ETRM metadata lists no formally registered referenced base objects for this view, so dependency tracking should be confirmed against ALL_DEPENDENCIES on the target instance. Conceptually, however, the join to HZ_PARTIES is what makes party-name resolution possible, and the process revision identifier ties each row to a specific revision of a process rather than to the process abstractly.

Key Columns

Common Use Cases and Queries

Typical reporting scenarios include ownership reporting, certification tracking, and process inventory extracts. A representative query resolving the application owner is:

  • SELECT process_id, name, process_display_name, application_owner_name, certification_status, approval_status_meaning FROM apps.amw_hierarchy_entities_v WHERE application_owner_name IS NOT NULL ORDER BY application_owner_name, name;

Other practical patterns include filtering on significant processes (WHERE significant_process_flag = 'Y'), aggregating process counts by owner, and generating navigation lists using URLSTRING. Because the view performs scalar lookup-function calls and multi-way party joins, queries should be restricted by process or owner criteria where possible to control execution cost on large hierarchies.