Results for “amw_wf_hierarchy_v”

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

Overview

AMW_WF_HIERARCHY_V is a database view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the AMW – Internal Controls Manager product. Its documented purpose is to return details about the Parent-Child Process Hierarchy used by the Oracle Workflow engine for the Internal Controls Manager process definitions. The view exposes the relationship between a workflow process and the activities (parent-child process steps) defined within it, filtered specifically to the AUDITMGR item type.

In the context of Oracle EBS 12.1.1 and 12.2.2, this view provides a reporting and integration layer over the underlying Workflow configuration tables, allowing administrators and developers to enumerate the process-to-activity hierarchy without querying the base Workflow tables directly. Because the view already restricts results to active (non-expired) records and excludes the START and END system activities, it serves as a convenient, pre-filtered source for hierarchical process reporting.

Underlying Base Objects

The view is defined over two Oracle Workflow base tables: WF_PROCESS_ACTIVITIES (aliased WPA) and WF_ACTIVITIES (aliased WA), with a correlated sub-query against WF_ACTIVITIES (aliased WA2). The join logic matches PROCESS_NAME, PROCESS_VERSION, and PROCESS_ITEM_TYPE between the process-activities table and the activities definition table.

Three filters shape the result set. First, the parent process activity is restricted to those where WA.END_DATE IS NULL, meaning the activity definition is currently active. Second, WPA.PROCESS_ITEM_TYPE must equal AUDITMGR, confining output to Internal Controls Manager workflow processes. Third, the correlated EXISTS clause against WA2 requires that the child activity also have END_DATE IS NULL, ensuring only currently valid child activities are returned. The NOT IN ('START', 'END') predicate removes the standard Workflow start and end marker activities.

Key Columns

• PARENT_PROCESS_NAME — The name of the parent workflow process being reported.
• PARENT_ITEM_TYPE — The item type of the parent process; effectively constrained to AUDITMGR by the view definition.
• CHILD_PROCESS_NAME — The name of the child activity or sub-process step contained within the parent process.
• CHILD_ITEM_TYPE — The item type associated with the child activity.

These four columns collectively describe the hierarchy edges between a parent process and its child activities, forming a directed relationship usable for recursive or tree-style reporting. The view text projects PROCESS_NAME, PROCESS_ITEM_TYPE, ACTIVITY_NAME, and ACTIVITY_ITEM_TYPE from the base query, which are surfaced through the documented column aliases.

Common Use Cases and Queries

A typical use case is enumerating all active child activities for the Internal Controls Manager processes, supporting audit-trail documentation and workflow administration review. A simple query lists the full parent-child relationship set:

• SELECT parent_process_name, child_process_name, child_item_type FROM apps.amw_wf_hierarchy_v ORDER BY parent_process_name, child_process_name;

To focus on a single parent process and its children:

• SELECT child_process_name, child_item_type FROM apps.amw_wf_hierarchy_v WHERE parent_process_name = :process_name;

Because the view filters on AUDITMGR and active activities automatically, no additional expiration or item-type predicates are required. It is frequently joined to other AMW reporting views to correlate process hierarchy with internal control definitions. Developers building custom Internal Controls Manager reports should note the view is read-only and inherits the security of the APPS schema; appropriate grants and synonyms must exist for non-APPS consumers. Its dependence on WF_ACTIVITIES also links it directly to the wf_activities base object referenced by users searching Workflow activity metadata.