Results for “waived_flag”

47 results




Overview
Explore in AI Chat

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

Overview

The AMW_VIOLATION_USERS table is a core transactional object within the Oracle E-Business Suite Internal Controls Manager (AMW) module. Its documented purpose is to store information about the violators associated with each violation record — that is, the specific users who breached a control rule, access policy, or segregation-of-duties constraint identified by the application. In Oracle EBS 12.1.1 and 12.2.2, this table underpins the auditing and compliance reporting functions that allow internal control officers to trace each exception to the responsible party.

From a Data Vault modeling perspective, the FK topology suggests a satellite-leaning classification. The table's primary key, USER_VIOLATION_ID, is a surrogate identifier, and its foreign key to AMW_VIOLATIONS indicates that the table hangs off a parent violation hub. The presence of descriptive attributes such as WAIVED_FLAG, CORRECTED_FLAG, and VIOLATED_BY_ID reinforces the satellite interpretation, as these columns track changing descriptive state rather than a standalone business entity.

Key Information Stored

The table contains eleven documented columns in the ETRM 12.1.1 physical schema. The most significant include:

  • USER_VIOLATION_ID — the surrogate primary key (AMW_VIOLATION_USERS_PK), uniquely identifying each violator row.
  • VIOLATION_ID — foreign key to AMW_VIOLATIONS, linking the violator record to its parent violation.
  • VIOLATED_BY_ID — the identifier of the user who committed or triggered the violation.
  • SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, enforcing multi-org and data-security partitioning.
  • WAIVED_FLAG — indicates whether the violation has been granted a waiver.
  • CORRECTED_FLAG — indicates whether the underlying violation has been remediated.
  • CREATION_DATE / CREATED_BY / LAST_UPDATE_DATE / LAST_UPDATED_BY / LAST_UPDATE_LOGIN — the standard EBS WHO columns providing audit trail and concurrency control.

No unique business-key index is documented beyond the primary key; VIOLATION_ID plus VIOLATED_BY_ID functions as a logical candidate key in practice.

Common Use Cases and Queries

Compliance officers and internal auditors use this table to enumerate violators per control exception, to report on outstanding versus waived or corrected items, and to drive remediation dashboards. Typical query patterns include joining to AMW_VIOLATIONS to retrieve violation context and joining to AMW_VIOLAT_USER_ENTRIES to expand the per-violator detail.

A representative SQL pattern:

  • SELECT vu.user_violation_id, vu.viollation_id, vu.violated_by_id, vu.waived_flag, vu.corrected_flag FROM amw.amw_violation_users vu WHERE vu.violation_id = :p_violation_id;
  • SELECT v.violation_name, vu.violated_by_id FROM amw.amw_violations v, amw.amw_violation_users vu WHERE v.violation_id = vu.violation_id AND vu.waived_flag = 'N' AND vu.corrected_flag = 'N';

Related Objects

The following objects are the most significant in relation to AMW_VIOLATION_USERS:

  • AMW_VIOLATIONS — parent table; joined on VIOLATION_ID.
  • AMW_VIOLAT_USER_ENTRIES — child table referencing USER_VIOLATION_ID, expanding the violator detail.
  • FND_SECURITY_GROUPS — joined on SECURITY_GROUP_ID to enforce data security.
  • FND_USER — referenced indirectly via VIOLATED_BY_ID to resolve the violator identity.
  • AMW_VIOLATION_USERS_PK — the primary key constraint that guarantees row uniqueness.
  • AMW Violation reporting views — OAM/AMW inquiry screens and concurrent programs that surface violator data for compliance reviews.