Search Results next_audit_date




Overview
Explore in AI Chat

Overview

AMW_PROCESS_HIERARCHY_V is a reporting view owned by the APPS schema within the Oracle E-Business Suite Internal Controls Manager (AMW) product family. It exposes the parent-child relationships that define the process hierarchy used by Internal Controls Manager, allowing consumers to traverse the structure of business processes modeled in the EBS workflow metadata repository. The view is documented as VALID in both Oracle EBS 12.1.1 and 12.2.2 and returns information about process hierarchy.

Because the object is a view rather than a base table, it presents no persisted data of its own; instead it joins workflow activity definitions with AMW process registrations to produce a flat, query-friendly representation of what is conceptually a tree. This makes it suitable for reporting, ad-hoc SQL, and integration extracts where a hierarchical parent-child listing is required without the caller needing to understand the underlying WF_ACTIVITIES and AMW_PROCESS data model.

Underlying Base Objects

Although the ETRM metadata records no documented base objects, the view text reveals its composition. It is defined over the following dictionary objects:

The joins require that parent and child activities are both currently active (WA.END_DATE IS NULL and WA2.END_DATE IS NULL) and that AMW process entries align with workflow activity names and item types. Translated display names are obtained through the language-specific TL tables, ensuring the view returns language-appropriate labels.

Key Columns

Common Use Cases and Queries

Typical usage includes rendering the process hierarchy in custom OAF or BI Publisher reports, driving drill-down navigation in Internal Controls Manager dashboards, and feeding hierarchy data into GRC or audit extracts. A basic query returning the parent-child structure is:

  • SELECT parent_process_id, child_process_id, parent_process_name, process_name FROM apps.amw_process_hierarchy_v ORDER BY parent_process_name, process_name;
  • SELECT parent_process_name, process_name FROM apps.amw_process_hierarchy_v WHERE parent_process_id = :process_id;
  • SELECT process_name, process_activity_type FROM apps.amw_process_hierarchy_v WHERE child_process_id = :child_id;

Because the ORG and status columns are null placeholders, consumers requiring organization, owner, or audit status information must join to the appropriate AMW tables rather than relying on this view alone. The view is best treated as a structural, hierarchy-only projection.