Search Results child_approval_end_date




Overview
Explore in AI Chat

Overview

AMW_CURR_APP_HIERARCHY_ORG_V is an APPS-owned database view in the Oracle E-Business Suite Release 12.1.1 and 12.2.2 environment, belonging to the AMW product family — Internal Controls Manager. The view exposes the currently approved organizational process hierarchy, denormalizing parent and child process records into a single flattened row per approved parent-child relationship. Its internal name, AMW_CURR_APP_HIERARCHY_ORG_V, combines "AMW," "CURR" (current), "APP" (approved), "HIERARCHY," and "ORG" (organization), reflecting its purpose: surfacing only those process hierarchy links that are valid as of the current system date.

The view plays a reporting and integration role. Downstream reports, dashboards, and ETL processes that need to traverse the approved process hierarchy for an organization — without writing the approval-date and end-date filtering logic themselves — can select directly from this view. Because it joins the process definition views to the approved hierarchy table, it centralizes the "what is currently approved and effective" business rule, promoting consistent behavior across Internal Controls Manager reporting.

Underlying Base Objects

The ETRM metadata lists no explicitly documented base objects under "Referenced base objects," but the view text itself reveals the three sources in its FROM clause:

  • AMW_PROCESS_ORGANIZATION_VL — referenced twice, as aliases PP (parent process) and CP (child process). This is the multi-language process definition view holding display names, descriptions, process codes, owners, approval attributes, and counts.
  • AMW_APPROVED_HIERARCHIES — aliased AH, the transactional table that stores the approved parent-child links between processes, including child ordering and effective start/end dates.

The join is driven by AH.PARENT_ID = PP.PROCESS_ID and AH.CHILD_ID = CP.PROCESS_ID, with organization and date filters ensuring parent and child belong to the same organization and both are currently approved and undated-deleted.

Key Columns

The view prefixes columns with PARENT_ or CHILD_ to preserve their provenance.

Common Use Cases and Queries

Typical uses include reconstructing an organization's approved process tree for compliance reporting, identifying significant processes and their owners, and driving Control Self-Assessment or certification workflows. A simple query lists children of a parent within an organization:

  • SELECT child_display_name, child_description, child_order_number FROM amw_curr_app_hier_org_v WHERE parent_process_id = :parent AND child_organization_id = :org ORDER BY child_order_number;
  • SELECT parent_display_name, child_display_name, child_control_count, child_certification_status FROM amw_curr_app_hier_org_v WHERE child_significant_process_flag = 'Y';

Because effective dating is already applied via SYSDATE predicates, no additional date filtering is required by callers.