Search Results amw_process_category

Overview

AMW_WF_HIERARCHY_ENTITIES_V is a reporting view owned by the APPS schema within the AMW – Internal Controls Manager product of Oracle E-Business Suite. Its documented purpose is to return details about processes, exposing process-level attributes alongside display-ready meanings and navigation URLs. The view is registered as VALID in both 12.1.1 and 12.2.2, and functions as a denormalized access point over the AMW process hierarchy so that downstream reports, Oracle Workflow-driven hierarchies, and integration layers do not need to reassemble lookup decoding and party resolution logic themselves.

Because the view resolves lookup codes into meanings via AMW_UTILITY_PVT.GET_LOOKUP_MEANING, and resolves owner identifiers into HZ party names, it is well suited to read-only presentation layers. The inclusion of prebuilt URL strings (URLSTRING and RISKCNTURL) indicates the view is also used to drive Oracle Application Framework (OAF) drill-down navigation from list-style regions.

Underlying Base Objects

The ETRM metadata does not document referenced base objects explicitly, but the view definition reveals its principal sources. The core driver is the AMW processes table referenced through the alias AMWP, supplying PROCESS_REV_ID, PROCESS_ID, PROCESS_CATEGORY, approval status, certification status, and the significant/standard process flags. A workflow entity table is referenced through alias WA, contributing NAME and ITEM_TYPE for the underlying Workflow item. Process display names are sourced from a translated table aliased WA_TL (DISPLAY_NAME). Owner identities are resolved from the HZ parties table through aliases HZP1, HZP2, and HZP3, corresponding to process owner, application owner, and finance owner respectively. Lookup decoding is delegated to the AMW_UTILITY_PVT package rather than to a join against FND_LOOKUPS.

Key Columns

• PROCESS_ID / PROCESS_REV_ID – Primary and revision identifiers for the process; also used in the DECODE logic that suppresses counts and URLs for the header row where PROCESS_ID = -1.
• PROCESS_DISPLAY_NAME – Translated display name of the process.
• NAME / ITEM_TYPE – Workflow entity name and item type associated with the hierarchy node.
• PROCESS_CATEGORY / PROCESS_CATEGORY_MEANING – The raw lookup code for the process category and its decoded meaning via the AMW_PROCESS_CATEGORY lookup type. This pairing is directly relevant to the search term "amw_process_category".
• SIGNIFICANT_PROCESS_FLAG / STANDARD_PROCESS_FLAG – Classification indicators used to filter scope in compliance reporting.
• APPROVAL_STATUS / APPROVAL_STATUS_MEANING / CERTIFICATION_STATUS / CERTIFICATION_STATUS_CODE – Status codes and their lookup meanings.
• RISK_COUNT / CONTROL_COUNT / ORG_COUNT – Aggregate counts, nulled for the -1 header row.
• PROCESS_OWNER_ID / PROCESS_OWNER_NAME, APPLICATION_OWNER_ID / APPLICATION_OWNER_NAME, FINANCE_OWNER_ID / FINANCE_OWNER_NAME – Owner identifiers paired with HZ party names.
• URLSTRING / RISKCNTURL – OAF navigation strings for process details and risk-tab drill-down.

Common Use Cases and Queries

The view is typically queried to list processes with human-readable categories and owners, or to filter by category for certification and risk-assessment reporting.

• Listing processes decoded by category:

  SELECT process_id, process_display_name, process_category_meaning,
         significant_process_flag, approval_status_meaning
  FROM   apps.amw_wf_hierarchy_entities_v
  WHERE  process_id <> -1
  AND    process_category_meaning = 'Financial';

• Identifying owners and count metrics for a compliance review:

  SELECT process_display_name, process_owner_name,
         application_owner_name, finance_owner_name,
         risk_count, control_count, org_count
  FROM   apps.amw_wf_hierarchy_entities_v
  WHERE  significant_process_flag = 'Y';

• Discovering the valid set of process categories in use:

  SELECT DISTINCT process_category, process_category_meaning
  FROM   apps.amw_wf_hierarchy_entities_v
  WHERE  process_category IS NOT NULL;

Note that the -1 header row must be excluded in most queries to avoid meaningless count and URL values, and that responsibility-level security is not enforced by the view itself.