Search Results process_org_id




Overview
Explore in AI Chat

Overview

AMW_ORG_HIERARCHY_ENTITIES_V is a view in the APPS schema that belongs to the AMW – Internal Controls Manager product within Oracle E-Business Suite 12.1.1 and 12.2.2. The ETRM metadata classifies this object with the status VALID and the description "Obsolete." Despite its valid dictionary state, the view is explicitly documented as obsolete, meaning it is retained only for backward compatibility with any dependent code, reports, or integration points that may still reference the object name. It returns no production data.

The view name suggests a historical role in exposing organization hierarchy entities, such as processes, risks, and controls, associated with Internal Controls Manager hierarchies. The presence of the column PROCESS_DISPLAY_NAME indicates the view was once used to present a user-facing label for a process entity, likely for hierarchical or reporting displays. In its current form, however, it serves as a null placeholder rather than a functional data source.

Underlying Base Objects

The documented view text defines AMW_ORG_HIERARCHY_ENTITIES_V as a single SELECT from DUAL. No base tables or other views are referenced. Every projected column is a literal NULL, cast to the appropriate type where needed via TO_NUMBER(NULL). The ETRM metadata confirms that no base objects are documented for this view.

Because the definition selects from DUAL, the view returns exactly one row containing all-null values. It does not read from any underlying Internal Controls Manager tables, nor does it join to organization, process, or hierarchy data. Any historical dependency on base tables has been removed, consistent with the "Obsolete" designation. From a dependency-tracking perspective, the view is isolated: it neither depends on nor exposes real application data.

Key Columns

The view exposes nineteen columns, all of which resolve to NULL at runtime:

  • PROCESS_ORG_ID, ORG_ID – Numeric identifiers that formerly linked a process entity to an organization unit.
  • ORG_NAME – The organization name associated with the hierarchy entity.
  • PROCESS_DISPLAY_NAME – The display label for the process; relevant to the user's search term and historically used in hierarchy presentations.
  • PROCESS_ID, NAME – The process identifier and its descriptive name.
  • ITEM_TYPE – A classifier distinguishing the entity type within the hierarchy.
  • SIGNIFICANT_PROCESS_FLAG, STANDARD_PROCESS_FLAG – Flags indicating whether the process is significant or standard in the internal controls context.
  • APPROVAL_STATUS – The workflow or approval state of the entity.
  • RISK_COUNT, CONTROL_COUNT – Aggregated counts of associated risks and controls.
  • PROCESS_OWNER_ID, PROCESS_OWNER_NAME – The owner of the process and the owner's display name.
  • CERTIFICATION_STATUS_CODE, CERTIFICATION_STATUS – Certification state information for the process.
  • URLSTRING, RISKCNTURL, CTRLCNTURL – Navigation or drill-down URL components used by the application interface.

None of these columns carry data in the current release, so they cannot be relied upon for functional queries or reports.

Common Use Cases and Queries

Because the view is obsolete and returns only nulls, it has no legitimate reporting or integration use case in 12.1.1 or 12.2.2. It should not be used to retrieve process hierarchy data, process display names, risk counts, control counts, ownership information, or certification status.

A query against the view succeeds but yields no meaningful output:

  • SELECT process_display_name, name, risk_count FROM apps.amw_org_hierarchy_entities_v;

This returns one row in which every column is NULL. Developers who encounter this view while tracing a legacy report or integration should treat it as a dead-end object and locate the current replacement view or table that provides organization hierarchy entity data within Internal Controls Manager. Any code still referencing AMW_ORG_HIERARCHY_ENTITIES_V should be reviewed and migrated to the supported data source, since reliance on this obsolete definition will produce empty result sets and may indicate broader compatibility cleanup work.