Search Results child_item_type




Overview
Explore in AI Chat

Overview

The view AMW_CURR_APP_HIERARCHY_RL_V belongs to the Oracle E-Business Suite module AMW – Internal Controls Manager, a component that Oracle has since classified as obsolete. Its stated purpose is to expose the risk library approved process hierarchy: a flattened, self-joined representation of approved processes and their parent–child relationships as recorded in the approved hierarchy structures of the Internal Controls Manager repository. In EBS 12.1.1 and 12.2.2 the object is documented in the ETRM metadata but is not implemented in the database, meaning the shipped schema does not physically create it in a standard installation. Where the view does exist, it functions as a reporting and integration surface for GRC-style analyses — scoping, certification, controls coverage and process roll-up — without requiring the caller to reconstruct the parent/child joins, date-effectivity predicates, or organization scoping manually.

Underlying Base Objects

Although the ETRM record lists no referenced base objects, the view text itself defines its sources explicitly. It is constructed from three objects joined in the main query and combined with a UNION branch:

  • AMW_PROCESS_VL — the process definition view, aliased twice as PR (parent) and CR (child).
  • AMW_APPROVED_HIERARCHIES — aliased AH, supplying the parent–child linkage and ordering.
  • A second SELECT branch unioned onto the first, which surfaces approved processes even where no hierarchy row qualifies, using TO_NUMBER(NULL) placeholders for the parent-side columns.

The join predicates enforce AH.PARENT_ID = PR.PROCESS_ID and AH.CHILD_ID = CR.PROCESS_ID, together with effectivity filters: hierarchy and process START_DATE less than or equal to SYSDATE, with END_DATE and APPROVAL_END_DATE either null or in the future. Rows with DELETION_DATE set are excluded, and the hierarchy is restricted to AH.ORGANIZATION_ID = -1, the sentinel used for global, non-organization-specific hierarchies. Because the composition is entirely view-based and no base tables are documented, the object should be treated as a read-only reporting construct rather than a transactional entity.

Key Columns

The projection is organized around a parent half and a child half. The parent columns are PARENT_PROCESS_ID, PARENT_REVISION_NUMBER, PARTENT_PROCESS_CODE (note the shipped spelling), PARENT_DISPLAY_NAME and PARENT_PROCESS_REV_ID. The child columns mirror these and add the richer attributes of the process definition: CHILD_PROCESS_CODE, CHILD_DISPLAY_NAME, CHILD_NAME, CHILD_ITEM_TYPE, CHILD_APPROVAL_STATUS, CHILD_START_DATE, CHILD_APPROVAL_DATE, CHILD_APPROVAL_END_DATE, CHILD_END_DATE, CHILD_CONTROL_COUNT, CHILD_RISK_COUNT, CHILD_ORG_COUNT, CHILD_SIGNIFICANT_PROCESS_FLAG, CHILD_STANDARD_PROCESS_FLAG, CHILD_CERTIFICATION_STATUS, CHILD_PROCESS_CATEGORY, CHILD_PROCESS_OWNER_ID, CHILD_FINANCE_OWNER_ID, CHILD_APPLICATION_OWNER_ID, CHILD_STANDARD_VARIATION and CHILD_ORDER_NUMBER. The user's search term, child_item_type, maps directly to CHILD_ITEM_TYPE, which distinguishes the type of the child node — typically separating process nodes from sub-process or risk/control nodes within the approved hierarchy. CHILD_ORDER_NUMBER preserves the sequence defined in AMW_APPROVED_HIERARCHIES, enabling deterministic ordering of siblings; CHILD_CERTIFICATION_STATUS and the owner identifiers support certification and accountability reporting.

Common Use Cases and Queries

Typical uses include process roll-up reports, hierarchy extracts for GRC dashboards, and integration feeds that need only currently approved relationships. A query filtering on the searched column is shown below.

  • Listing approved child nodes of a given type for a parent process.
  • Counting controls and risks per child, ordered by CHILD_ORDER_NUMBER.
  • Identifying certified versus uncertified processes by owner.
SELECT parent_process_code,
       child_process_code,
       child_item_type,
       child_display_name,
       child_control_count,
       child_risk_count
  FROM amw_curr_app_hierarchy_rl_v
 WHERE nvl(child_item_type, 'PROCESS') = 'PROCESS'
 ORDER BY parent_process_code, child_order_number;

Because the view is obsolete and, per the ETRM metadata, not implemented in this database, any dependent custom code should be validated against the actual installation before use; where absent, the equivalent logic must be reproduced directly against AMW_PROCESS_VL and AMW_APPROVED_HIERARCHIES.