Search Results amw_process_org_hierarchy_v




Overview
Explore in AI Chat

Overview

AMW_PROCESS_ORG_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 information about the Process Organization Hierarchy. In practice, the view exposes a normalized parent–child relationship between processes and the organizations that own them, allowing reporting and integration components to navigate from a parent process identifier to its child process identifier without repeatedly querying the underlying hierarchy structures. The view carries a VALID status in both Oracle EBS 12.1.1 and 12.2.2, indicating it is a supported, queryable object.

Because Internal Controls Manager relies heavily on process hierarchies for scoping, risk assessment, and control testing, this view acts as a lightweight traversal surface. Rather than exposing the full attribute set of a process, it projects only the two columns required to define edges in the hierarchy graph, which makes it efficient for recursive queries and for populating tree or org-chart style displays in downstream reporting tools.

Underlying Base Objects

The ETRM metadata documents no referenced base tables and lists no separately documented base objects. However, the published view text reveals that AMW_PROCESS_ORG_HIERARCHY_V is defined as a union over the following:

The union therefore produces the complete set of parent–child edges: all real hierarchy links plus a synthetic edge that anchors every top-level process to a common root node identified by -1. This design is common in AMW hierarchy views, where a virtual root is useful for rendering a single connected tree.

Key Columns

The view exposes exactly two columns:

  • PARENT_PROCESS_ID — the identifier of the parent node in the hierarchy. For real hierarchy rows this value corresponds to an actual AMW process identifier inherited from AMW_PROCESS_HIERARCHY_V. For synthetic root rows it is the constant -1.
  • CHILD_PROCESS_ID — the identifier of the child node. This is the column most often referenced when resolving which processes sit beneath a given parent, and it is the column cited in the search term "child_process_id." For synthetic rows it holds AMWPOBV.TOP_PROCESS_ID, i.e., the top process of an organization.

Because the view projects only these two identifiers, consumers must join back to process or organization detail views to obtain names, descriptions, or statuses. The synthetic -1 parent value should be handled explicitly in any query logic, since it does not correspond to a stored process record.

Common Use Cases and Queries

Typical scenarios include recursive expansion of a process tree, determining the immediate children of a process for approval routing, and reconciling process ownership against organizations. To list direct children of a given process:

  • SELECT child_process_id FROM apps.amw_process_org_hierarchy_v WHERE parent_process_id = :p_process_id;

To retrieve all top-level processes anchored to the synthetic root:

  • SELECT child_process_id FROM apps.amw_process_org_hierarchy_v WHERE parent_process_id = -1;

For full downward traversal, the view is commonly used inside a CONNECT BY query:

  • SELECT child_process_id FROM apps.amw_process_org_hierarchy_v START WITH parent_process_id = -1 CONNECT BY PRIOR child_process_id = parent_process_id;

Because only two columns are returned, joins to AMW process master data are required whenever human-readable output is needed. This view is best treated as a navigational index rather than a reporting source in its own right.