Search Results amw_constraint_entries

Overview

The AMW_CONSTRAINT_ENTRIES table is a core data object within the Oracle E-Business Suite (EBS) module for Internal Controls Manager (AMW). It functions as the detailed repository for defining incompatible functions within a segregation of duties (SoD) or business control constraint. A constraint is a rule that prevents users from holding access to two or more functions that, when combined, could create a risk of fraud or error. This table stores the specific list of functions that are deemed incompatible with each other under a given constraint rule, enabling the system to perform automated access violation checks against user responsibilities.

Key Information Stored

The table's primary role is to map individual functions to their parent constraint definitions. While the full column list is not detailed in the provided metadata, the documented foreign keys and description reveal critical data points. The CONSTRAINT_REV_ID column links each entry to a specific constraint definition in the AMW_CONSTRAINTS_B table. The FUNCTION_ID column stores the identifier for an incompatible function, which corresponds to a record in the FND_FORM_FUNCTIONS table. The OBJECT_TYPE column, as noted in the description, is used to identify the type of the incompatible function. The metadata specifies that 'FUNC' is one possible value, indicating the FUNCTION_ID references a standard EBS function. This structure allows for the precise definition of risk conflicts within the Internal Controls Manager framework.

Common Use Cases and Queries

This table is central to compliance reporting and access analysis. A primary use case is generating a detailed report of all incompatible function pairs defined in the system for audit purposes. System administrators may query this table to understand the specific functions involved when a user violates a constraint during responsibility assignment. A typical analytical query would join AMW_CONSTRAINT_ENTRIES with AMW_CONSTRAINTS_B to get the constraint name and with FND_FORM_FUNCTIONS to resolve the function IDs into user-readable function names. For example, to list all incompatible function pairs for a given constraint, one might use a self-join or analytical SQL to pair entries sharing the same CONSTRAINT_REV_ID.

Related Objects

• AMW_CONSTRAINTS_B: This is the master table for constraint definitions. The AMW_CONSTRAINT_ENTRIES.CONSTRAINT_REV_ID column is a foreign key to this table, establishing that each entry belongs to a specific constraint rule.
• FND_FORM_FUNCTIONS: This is the core Oracle EBS table storing all application function definitions. The AMW_CONSTRAINT_ENTRIES.FUNCTION_ID column is a foreign key to FND_FORM_FUNCTIONS.FUNCTION_ID, resolving the incompatible entry to a specific executable function within the system.