Search Results requested_by_name




Overview
Explore in AI Chat

Overview

APPS.AMW_VIOLATIONS_V is a public Oracle E-Business Suite view owned by the APPS schema and registered under FND Design Data as AMW.AMW_VIOLATIONS_V. It exposes information about Segregation of Duties (SoD) constraint violations recorded by the Application Access Controls Governor / E-Business Suite Risk Management components of Oracle Governance, Risk, and Compliance (GRC). The view is documented as valid in both release 12.1.1 and 12.2.2 environments, and Oracle classifies it as a public view that may be useful for custom reporting or other data requirements.

Because it consolidates constraint definitions, employee identity, and violation results into a single denormalized result set, the view is particularly convenient for audit reporting, control monitoring dashboards, and integration routines that need to consume SoD exception data without joining the underlying transactional tables directly. The user search term "violator_num" corresponds to VIOLATOR_NUM, one of the view's documented numeric columns, which identifies the number of the violator associated with a given constraint violation record.

Underlying Base Objects

Per the ETRM metadata, APPS.AMW_VIOLATIONS_V is defined over the following database objects: AMW_CONSTRAINTS_VL, AMW_EMPLOYEES_CURRENT_V, AMW_LOOKUPS, and AMW_VIOLATIONS. The view does not reference, and is not referenced by, any other documented database objects.

  • AMW_VIOLATIONS — the primary transactional store of constraint violation records generated during a validation request.
  • AMW_CONSTRAINTS_VL — the translated constraint definition view, supplying the constraint name and constraint type description.
  • AMW_EMPLOYEES_CURRENT_V — resolves the requesting user to a current employee full name and identifier.
  • AMW_LOOKUPS — provides the decoded meaning and code for the violation status.

The joins among these objects produce one row per constraint violation, enriched with constraint, requester, and status context.

Key Columns

  • VIOLATION_ID (NUMBER) — unique identifier for the violation record.
  • VIOLATOR_NUM (NUMBER) — the number of the violator, typically corresponding to the person or assignment that breached the SoD constraint and the value most often used to pivot violation counts by individual.
  • CONSTRAINT_NAME (VARCHAR2 240) and CONSTRAINT_REV_ID (NUMBER) — the violated constraint and its revision.
  • TYPE_DESCRIPTION (VARCHAR2 240) — textual description of the constraint type.
  • REQUEST_ID, REQUEST_DATE, REQUESTED_BY_ID, REQUESTED_BY_NAME — identify the validation run and the user who submitted it.
  • STATUS_CODE (VARCHAR2 30) and STATUS_MEANING (VARCHAR2 80) — the coded and decoded status of the violation.

Common Use Cases and Queries

Typical uses include auditing SoD exceptions by violator, trending violations across validation requests, and feeding external GRC or identity-management platforms. The following sample lists violations for a specific violator number:

  • SELECT constraint_name, constraint_rev_id, request_id, request_date, violator_num, requested_by_name, status_meaning, type_description FROM apps.amw_violations_v WHERE violator_num = :violator_num;
  • SELECT violator_num, COUNT(*) violations FROM apps.amw_violations_v WHERE status_code = 'OPEN' GROUP BY violator_num ORDER BY violations DESC;
  • SELECT request_id, request_date, requested_by_name, constraint_name, violator_num, status_meaning FROM apps.amw_violations_v WHERE request_date >= :from_date ORDER BY request_date DESC;

All queries should be executed with the APPS schema context or a synonym granted to the reporting user, consistent with Oracle's recommendation for public views.