Results for “parent_id”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

AMW_LATEST_HIERARCHIES is a table owned by the AMW schema, the database account associated with the Internal Controls Manager module in Oracle E-Business Suite. Its documented purpose is to store the latest process and organization process hierarchies — the current, flattened parent-child structure of processes and organizational process trees used by the compliance and controls functionality. The table is documented in ETRM reference material for both EBS 12.1.1 and 12.2.2.

Two important caveats apply. First, AMW is flagged as obsolete in the documentation; the Internal Controls Manager product line is no longer actively implemented. The ETRM implementation note for this object states "Not implemented in this database," meaning the table may not physically exist in every environment. Second, the heuristic Data Vault classification derived from its foreign key structure is standalone, which suggests the table behaves as an independent hub-like structure rather than as a link or satellite: it holds the current hierarchy snapshot keyed chiefly by its own business identifiers rather than serving purely as an associative or descriptive entity.

Key Information Stored

The documented physical schema comprises 11 columns. The most significant are the hierarchy identity and structure columns:

• ORGANIZATION_ID — identifies the operating unit or organization context for the hierarchy.
• PARENT_ID — the parent node in the process or organization process tree.
• CHILD_ID — the child node beneath that parent.
• CHILD_ORDER_NUMBER — sequence position of the child among its siblings, controlling display ordering.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, governing row-level access control.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard EBS audit trail columns.
• CREATION_DATE, CREATED_BY — row creation audit columns.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the OAF/ADF framework.

The unique index AMW_LATEST_HIERARCHIES_U1 covers (ORGANIZATION_ID, PARENT_ID, CHILD_ID), making this composite the business-key candidate. Because the documented column list does not include a separate surrogate sequence column, the organization/parent/child triplet effectively serves as the row identifier.

Common Use Cases and Queries

The primary use case is reconstructing the current process hierarchy for a given organization. A typical query joins parent and child identifiers back to the process definition tables to produce a readable tree:

• Reporting the current hierarchy: SELECT ORGANIZATION_ID, PARENT_ID, CHILD_ID, CHILD_ORDER_NUMBER FROM AMW_LATEST_HIERARCHIES WHERE ORGANIZATION_ID = :org ORDER BY PARENT_ID, CHILD_ORDER_NUMBER;
• Finding all descendants of a node via recursive CONNECT BY on PARENT_ID / CHILD_ID.
• Validating hierarchy completeness by comparing node coverage against the master process table.
• Auditing changes using LAST_UPDATE_DATE and LAST_UPDATED_BY for compliance reviews.

Because Internal Controls Manager is obsolete, queries against this table are typically confined to historical or migration contexts rather than active production reporting.

Related Objects

The documented foreign key relationship is:

• FND_SECURITY_GROUPS — referenced via SECURITY_GROUP_ID, providing the security grouping that restricts visibility of hierarchy rows.

Additional objects that logically participate in the hierarchy model include the AMW process definition tables (parent and child process entities referenced by PARENT_ID and CHILD_ID) and the standard EBS audit columns sourced from FND_STANDARD audit conventions. Join paths should be validated against the target environment, since the table is documented as not implemented in all databases.