Search Results amw_constraints_b




Overview
Explore in AI Chat

Overview

The AMW_CONSTRAINTS_B table is a core data object within the AMW (Internal Controls Manager) module of Oracle E-Business Suite (EBS) versions 12.1.1 and 12.2.2. It serves as the master repository for Segregation of Duties (SoD) constraint definitions. These constraints are formal business rules designed to mitigate risk by preventing a single user from performing incompatible combinations of functions or responsibilities within the application. The table's role is foundational to the Internal Controls Manager's ability to define, manage, and subsequently identify violations of these critical security and compliance policies.

Key Information Stored

As a base table, AMW_CONSTRAINTS_B holds the essential metadata for each SoD constraint. Its primary key, CONSTRAINT_REV_ID, uniquely identifies each constraint revision, supporting versioning and auditability of rule changes over time. While the full column list is not detailed in the provided metadata, typical columns in such a table would include fields for the constraint name, a detailed description, its current status (e.g., 'Active', 'Inactive'), effective dates, and identifiers for the owning organization or risk model. The presence of a revision ID in the primary key suggests the table is designed to maintain a history of constraint modifications.

Common Use Cases and Queries

The primary use case is the administration and analysis of SoD controls. Common operational and reporting queries involve listing all active constraints, identifying constraints associated with specific risks, or auditing constraint changes. For instance, to retrieve a basic list of constraints, a query would join with descriptive tables (like AMW_CONSTRAINTS_TL for translated names) using the CONSTRAINT_REV_ID. The table is also central to the violation detection engine; the system cross-references user assignments against the rules stored here to populate the AMW_VIOLATIONS table. A typical analytical query might join AMW_CONSTRAINTS_B to AMW_VIOLATIONS to report on all violations by constraint name and severity.

Related Objects

AMW_CONSTRAINTS_B has defined foreign key relationships with several other critical AMW tables, establishing its role as a parent entity. The documented relationships are:

  • AMW_CONSTRAINT_ENTRIES: This table references AMW_CONSTRAINTS_B via the column AMW_CONSTRAINT_ENTRIES.CONSTRAINT_REV_ID. It stores the individual function or responsibility entries that make up the incompatible combinations defined in the parent constraint.
  • AMW_VIOLATIONS: This table references AMW_CONSTRAINTS_B via the column AMW_VIOLATIONS.CONSTRAINT_REV_ID. It records instances where a user's assigned permissions breach a specific constraint, directly linking each violation to the rule that was violated.

These relationships form the core data model for defining a constraint (via entries) and reporting its breaches (via violations).