Search Results child_control_activity_type




Overview
Explore in AI Chat

Overview

AMW_LEGAL_HIER_V is a reporting view in the Oracle E-Business Suite Internal Controls Manager (ICM) product family, delivered under the AMW schema prefix. Its documented purpose is to expose the legal hierarchy of organizations as maintained within the ICM audit and organizational structure model. In EBS 12.1.1 and 12.2.2, this view belongs to the Internal Controls Manager module, which is marked obsolete in the documented metadata. The "Not implemented in this database" annotation indicates that the view is a legacy definition carried forward in the ETRM reference material rather than an actively installed database object in the environment from which the metadata was extracted. Practically, AMW_LEGAL_HIER_V presents a flattened, union-based representation of the legal entity hierarchy, deriving its parent-child relationships from Oracle General Ledger key flexfield value sets that are designated as subsidiary value sets within ICM audit units.

Underlying Base Objects

No base objects are documented as dependencies in the supplied ETRM metadata, so the view definition must be read directly from the stored text. Two Oracle Applications foundation views are referenced explicitly: FND_FLEX_VALUES_VL, which supplies the value set identifier, flex value, flex value identifier, and description for each legal entity value; and FND_FLEX_VALUE_CHILDREN_V, which supplies the parent-child hierarchy relationships within a value set. The filter logic restricts rows to value sets that appear as SUBSIDIARY_VALUESET in AMW_AUDIT_UNITS_V, and further restricts to enabled values (ENABLED_FLAG = 'Y'). The first branch of the UNION returns top-level flex values that are not listed as children in FND_FLEX_VALUE_CHILDREN_V, treating them as root legal entities. The second branch returns child relationships, joining parent and child flex values back to FND_FLEX_VALUES_VL to resolve parent and child identifiers and display names. Because the view depends on ICM audit unit configuration, its output is meaningful only where AMW setup data is present.

Key Columns

The view projects a fixed, wide column list with LINE_TYPE hard-coded to 'COMPANY' in the documented branch. The principal structural columns are FLEX_VALUE_SET_ID, PARENT_VALUE, PARENT_ID, and PARENT_DISPLAY_NAME, which together describe the position of a node within the legal hierarchy. CHILD_VALUE, CHILD_ID, and CHILD_DISPLAY_NAME describe the node itself. Several columns are explicitly NULL in the documented definition, including CHILD_CONTROL_COUNT, CHILD_RISK_COUNT, CHILD_SIGNIFICANT_PROCESS_FLAG, CHILD_STANDARD_PROCESS_FLAG, CHILD_CERTIFICATION_STATUS, CHILD_PROCESS_CATEGORY, CHILD_PROCESS_TYPE, CHILD_CONTROL_ACTIVITY_TYPE, CHILD_ORDER_NUMBER, and ACTIVE_AUDIT_PROJECT_COUNT. These placeholders exist to provide a uniform column contract that parallels the process and control hierarchy views in the same family. The user query term "child_control_count" corresponds directly to the CHILD_CONTROL_COUNT column, which in this legal-hierarchy view is a structural placeholder rather than a populated measure.

Common Use Cases and Queries

Because CHILD_CONTROL_COUNT and related count columns are defined as NULL here, this view is used primarily to render the legal entity tree for ICM navigation, security, and reporting rather than to aggregate control or risk volumes. Typical queries enumerate legal entities and their parents for a subsidiary value set, or locate root legal entities for audit scoping.

  • List all legal entities and their parents:
    SELECT flex_value_set_id, parent_value, child_value, child_display_name FROM amw_legal_hier_v ORDER BY flex_value_set_id, parent_value, child_value;
  • Retrieve only root legal entities:
    SELECT child_value, child_id, child_display_name FROM amw_legal_hier_v WHERE parent_value IS NULL;
  • Restrict to a specific subsidiary value set:
    SELECT * FROM amw_legal_hier_v WHERE flex_value_set_id = :p_valueset_id;

Consumers should confirm the view's installation status in their environment, since the ETRM metadata records it as not implemented, and validate results against FND_FLEX_VALUES_VL and FND_FLEX_VALUE_CHILDREN_V directly where the view is absent.