Results for “responsibility_id”

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

Overview

AMW_ROLE_CONSTRAINT_DENORM is a denormalized table in the AMW (Internal Controls Manager) schema of Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the flattened "Menu/Function Structure within Responsibility" representation used by Internal Controls Manager when evaluating Potential Responsibility Violations against defined segregation-of-duties constraints. Because the table preserves the full menu-to-function expansion for a responsibility, it allows ICM's constraint engine to detect whether a single responsibility grants access to combinations of functions that violate a control rule, without re-walking the underlying menu hierarchy at runtime.

From a Data Vault modeling perspective, the metadata's heuristic classification is standalone. In practical terms, this object behaves less like a pure hub, link, or satellite and more like a derived denormalized fact/bridge structure: it carries descriptive attributes (ROLE_NAME, OBJECT_TYPE, GROUP_CODE) alongside foreign references to FND_MENUS and AMW_CONSTRAINTS_B, making it a candidate for a link-satellite pattern across responsibility, menu, and constraint dimensions.

Key Information Stored

The table carries 12 documented columns. The most significant include:

• ROLE_NAME — The responsibility name being evaluated; the primary business identifier for the denormalized row and a candidate business key.
• RESPONSIBILITY_ID — Surrogate reference to the responsibility (typically matching FND_RESPONSIBILITY.RESPONSIBILITY_ID), linking the row to a concrete application responsibility.
• MENU_ID — Foreign key to FND_MENUS, identifying the menu within the responsibility's hierarchy.
• CONSTRAINT_REV_ID — Foreign key to AMW_CONSTRAINTS_B, identifying the specific constraint revision the violation analysis relates to.
• FUNCTION_ID — The function reached under the menu; the leaf-level access point used for SoD evaluation.
• OBJECT_TYPE — Classifies the denormalized element (e.g., menu vs. function vs. submenu).
• GROUP_CODE — Grouping attribute used to organize or partition the constraint evaluation results.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATION_DATE, CREATED_BY — Standard EBS WHO columns providing audit lineage.

No explicit surrogate primary key column is identified in the documented metadata; the natural composite of ROLE_NAME/RESPONSIBILITY_ID, MENU_ID, FUNCTION_ID, and CONSTRAINT_REV_ID functions as the effective business key.

Common Use Cases and Queries

The primary use case is SoD violation reporting: identifying responsibilities whose menu/function expansion overlaps with functions restricted by a constraint. A typical query joins to AMW_CONSTRAINTS_B to retrieve constraint detail:

• SELECT rc.ROLE_NAME, rc.RESPONSIBILITY_ID, rc.FUNCTION_ID, cb.CONSTRAINT_NAME FROM AMW_ROLE_CONSTRAINT_DENORM rc, AMW_CONSTRAINTS_B cb WHERE rc.CONSTRAINT_REV_ID = cb.CONSTRAINT_ID;
• Filtering by ROLE_NAME to enumerate every menu/function pair expanding a single responsibility.
• Aggregating by GROUP_CODE to summarize violation counts per control group.
• Joining to FND_MENUS to trace the top-level menu context for each flagged function.

Because the table is denormalized, it supports fast reporting without recursive menu traversal, making it well-suited for periodic ICM certification and audit extracts.

Related Objects

• FND_MENUS — joined via MENU_ID; provides the menu definition backing each denormalized row.
• AMW_CONSTRAINTS_B — joined via CONSTRAINT_REV_ID; supplies the constraint definition/revision being evaluated.
• FND_RESPONSIBILITY — logically related via RESPONSIBILITY_ID/ROLE_NAME for responsibility metadata.
• FND_FUNCTION / FND_FORM_FUNCTIONS — logically related via FUNCTION_ID for function definitions.
• Other AMW tables (constraint definitions, violation results, and role/menu snapshots) that consume this denormalized structure during ICM constraint processing.