Search Results application_owner_id




Overview
Explore in AI Chat

Overview

AMW_WF_HIERARCHY_MAIN_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the AMW — Internal Controls Manager product. The view exposes the parent-child process hierarchy used by Internal Controls Manager's workflow-driven process library, returning one row per parent process / child activity pairing along with a substantial set of descriptive and status attributes for the process itself. Because AMW's process hierarchy is modelled on the Workflow (WF) engine, the view resolves the relationship between a parent workflow process and the child subprocess or activity nested beneath it, then enriches that relationship with process metadata such as ownership, approval status, certification status, risk and control counts, and organisation counts.

The view is read-oriented and is typically consumed by OAF-based AMW pages, risk library listings, and custom extracts that need to report on the control framework. Its relevance to a search on application_owner_id is direct: the column APPLICATION_OWNER_ID is projected by this view, joined to HZ_PARTIES to resolve the application owner's display name, and is distinct from PROCESS_OWNER_ID, which identifies the process owner.

Underlying Base Objects

The documented view text is defined over WF_PROCESS_ACTIVITIES (aliased WPA), which supplies the parent process name and item type together with the child activity name and item type; and over AMW process tables (aliased AMWP) that supply the process revision, process identifier, flags, counts, statuses, and owner identifiers. Party names are resolved through two aliases of HZ_PARTIES — HZP1 for PROCESS_OWNER_NAME and HZP2 for APPLICATION_OWNER_NAME. Lookup meanings are resolved through AMW_UTILITY_PVT.GET_LOOKUP_MEANING against lookup types AMW_CERTIFICATION_STATUS, AMW_PROCESS_APPROVAL_STATUS, and AMW_PROCESS_CATEGORY. Transition ordering is computed by AMW_WF_HIERARCHY_PKG.FIND_TRANSITION_ORDER. Subqueries against WF_PROCESS_ACTIVITIES derive the maximum INSTANCE_ID for each parent/child combination, which is then passed to the hierarchy package. No base objects are separately documented in the ETRM metadata for this view beyond the text above.

Key Columns

Common Use Cases and Queries

Typical scenarios include reporting the full parent-child process tree for audit and SOX documentation, listing processes by application owner, and reconciling AMW risk and control counts against the process library.

  • Identify all processes for a given application owner: 
    SELECT parent_process_name,
       child_process_name,
       process_display_name,
       application_owner_name
  FROM apps.amw_wf_hierarchy_main_v
 WHERE application_owner_id = :p_application_owner_id;
  • Drill from an application owner down to approval and certification state: 
    SELECT application_owner_name,
       process_display_name,
       approval_status_meaning,
       certification_status,
       risk_count,
       control_count
  FROM apps.amw_wf_hierarchy_main_v
 WHERE application_owner_id IS NOT NULL
 ORDER BY application_owner_name, process_display_name;
  • Report the hierarchy with transition ordering for a single parent process: 
    SELECT parent_process_name,
       child_process_name,
       transition_reverse_order,
       instance_id
  FROM apps.amw_wf_hierarchy_main_v
 WHERE parent_process_name = :p_parent_process
 ORDER BY transition_reverse_order;

Because the view performs correlated subqueries and function calls per row, queries should be filtered by parent process, process ID, or owner where possible to limit full scans of the underlying workflow activity data.