Search Results user_violation_id

Overview

The AMW.AMW_VIOLATION_USERS table is a core data repository within the Oracle E-Business Suite (EBS) Application Management (AMW) module, specifically for versions 12.1.1 and 12.2.2. It serves as the transactional table for recording and managing user-level violations identified by the system's compliance and control monitoring engines. Its primary role is to store the specific instances where a user's access or activity violates a defined security or segregation of duties (SoD) constraint. Each row represents a unique violation occurrence for a single user, linked to the overarching control rule, enabling administrators to track, waive, and correct individual user compliance issues.

Key Information Stored

The table's structure is designed to capture the violation instance, its status, and standard audit information. The most critical columns include:

• USER_VIOLATION_ID: The primary key uniquely identifying each user violation record.
• VIOLATION_ID: A foreign key linking to AMW_VIOLATIONS, identifying the specific control or constraint that was breached.
• VIOLATED_BY_ID: Stores the identifier (typically FND_USER.USER_ID) of the user who committed the violation.
• WAIVED_FLAG: Indicates if the violation has been formally waived ('Y') or is active ('N' or NULL).
• CORRECTED_FLAG: Tracks if the underlying access issue has been remediated ('Y') or not ('N' or NULL).
• Standard Who Columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN): Provide audit trails for record creation and modification.
• SECURITY_GROUP_ID: Supports data partitioning in multi-org or hosted environments.

Common Use Cases and Queries

This table is central to compliance reporting and violation lifecycle management. Common operational scenarios include generating active violation reports for audit purposes, tracking remediation progress, and managing waiver justifications. A fundamental query to retrieve all violation details for analysis is directly provided by the ETRM:

SELECT LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATION_DATE, CREATED_BY, SECURITY_GROUP_ID, VIOLATED_BY_ID, VIOLATION_ID, USER_VIOLATION_ID, WAIVED_FLAG, CORRECTED_FLAG FROM AMW.AMW_VIOLATION_USERS;

Practical extensions include joining with FND_USER to get usernames and with AMW_VIOLATIONS for constraint details. For example, a report of all non-waived, uncorrected violations for a specific user would filter on `VIOLATED_BY_ID`, `WAIVED_FLAG = 'N'`, and `CORRECTED_FLAG = 'N'`. System processes also query this table to determine if a user's access request would create a new violation record.

Related Objects

The AMW_VIOLATION_USERS table exists within a defined relational schema, as evidenced by its foreign key constraints.

• Primary Key: AMW_VIOLATION_USERS_PK on USER_VIOLATION_ID.
• Foreign Key (Outbound): The VIOLATION_ID column references the AMW_VIOLATIONS table. This is the critical link to the definition of the control rule that was violated.
• Foreign Key (Inbound): The table is referenced by the AMW_VIOLAT_USER_ENTRIES table via the USER_VIOLATION_ID column. This suggests a more granular breakdown, where a single user violation (e.g., an SoD conflict) may be comprised of multiple violating "entries" or individual role assignments.