Search Results find_hierarchy_children

Overview

The AMW_WF_HIERARCHY_PKG package body in the APPS schema supports the Oracle E-Business Suite Audit Management and Workflow (AMW) product family, which is part of the Oracle Enterprise Governance, Risk, and Compliance (EGRC) suite. Its principal responsibility is to synchronize and reconcile organizational hierarchies, process hierarchies, and workflow activity structures so that audit, risk, and control objects are aligned with the HR organization hierarchy and the Oracle Workflow (WF) definitions that drive AMW business processes. In Oracle EBS 12.1.1 and 12.2.2, this package is a critical internal utility invoked during hierarchy maintenance, process reorganization, and workflow-driven state changes. It underpins the denormalized hierarchy tables that AMW uses for high-performance traversal of process, organization, and workflow relationships.

Key Procedures and Functions

The documented package exposes 43 procedures and functions. Core hierarchy traversal logic is provided by FIND_HIERARCHY_CHILDREN, FIND_HIERARCHY_PARENT, FIND_ORG_HIERARCHY_PARENT, and FIND_ORG_HIERARCHY_CHILDREN, which walk the process and organization hierarchy trees respectively. FIND_TRANSITION_ORDER and FIND_TRANSITION_CHILDREN resolve ordering and child relationships within workflow activity transitions, enabling correct process sequencing.

Process and workflow synchronization is handled by SYNCH_HIERARCHY_AMW_PROCESS and ADHOC_SYNCH_HIER_AMW_PROC, which rebuild or refresh hierarchy structures when AMW process definitions or their workflow counterparts change. WRITE_AMW_PROCESS and POPULATE_FLATLIST persist process records and build the flattened hierarchy list used for fast lookups.

Organization association logic includes CREATE_ORG_RELATIONS, ASSOC_PROCESS_ORG_HIER, ASSOC_PROCESS_RCM_ORG_HIER, ASSOCIATE_ORG_PROCESS, MODIFY_ORG_RELATION, DELETE_ORG_RELATION, DISASSOCIATE_PROCESS_ORG, and DISASSOC_PROC_ORG_HIER — all managing the mapping between AMW processes and the organizations or RCM org hierarchies they apply to. RESET_PROCESS_RISK_CTRL_COUNT and RESET_PROC_ORG_RISK_CTRL_COUNT maintain denormalized counters for risk and control associations per process and per process-organization combination.

Tables Accessed

The package reads and writes AMW_PROCESS and AMW_PROCESS_S for process definitions, AMW_PROCESS_ORGANIZATION and AMW_PROCESS_ORG_RELATIONS for process-to-organization mapping, and the denormalized AMW_PROC_HIERARCHY_DENORM and AMW_ORG_HIERARCHY_DENORM tables for flattened hierarchy storage. Exception handling references AMW_EXCEPTIONS_B, AMW_EXCEPTIONS_REASONS, and AMW_EXCEPTIONS_TL. Risk, control, and objective linkage is supported through AMW_CONTROL_ASSOCIATIONS, AMW_RISK_ASSOCIATIONS, and AMW_OBJECTIVE_ASSOCIATIONS, while counting logic reads these tables to refresh denormalized totals.

Organization structure data is sourced from HR_ORGANIZATION_INFORMATION, PER_ORGANIZATION_STRUCTURES, PER_ORG_STRUCTURE_ELEMENTS, and PER_ORG_STRUCTURE_VERSIONS. Workflow integration uses WF_ACTIVITIES, WF_ACTIVITIES_TL, WF_ACTIVITY_TRANSITIONS, WF_PROCESS_ACTIVITIES, and WF_PURGE. Utility views include AMW_AUDIT_UNITS_V, AMW_EMPLOYEES_CURRENT_V, AMW_PROCESS_HIERARCHY_V, and AMW_WF_HIERARCHY_V. Standard FND packages (FND_API, FND_CONCURRENT, FND_FILE, FND_GLOBAL, FND_MESSAGE, FND_MSG_PUB, FND_PROFILE, FND_USER) supply API error handling, concurrency, messaging, and user context. Internal collaborators include AMW_PROC_ORG_HIERARCHY_PVT and AMW_UTILITY_PVT.

Usage Notes

AMW_WF_HIERARCHY_PKG is not referenced by any other database object, confirming it is a top-level internal utility invoked by AMW forms, concurrent programs, and workflow background processes rather than by external APIs. It is typically called when an administrator creates, modifies, or reorganizes a process hierarchy, or when an AMW process is associated with or disassociated from an operating unit or RCM organization hierarchy. Synchronization procedures such as SYNCH_HIERARCHY_AMW_PROCESS and ADHOC_SYNCH_HIER_AMW_PROC are commonly triggered from concurrent program submissions and are dependent on FND_CONCURRENT and FND_FILE for logging. Because the package is classified as OTHER and is undocumented for public use, customizations should not call it directly; instead, administrators should use the supported AMW setup forms and concurrent programs that invoke it internally.