Search Results ap_pol_violations_all




Overview
Explore in AI Chat

Overview

AP_POL_VIOLATIONS_ALL is a Payables (AP) module table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores policy violation information detected against expense reports. Each row captures a single violation raised when an expense report line breaches a configured expense policy — for example, exceeding a permitted meal, lodging, or mileage limit. The table is owned by the AP schema and is classified as VALID in the ETRM data dictionary.

Because expense policy checks are evaluated per distribution line, and the same line may simultaneously violate more than one rule, the table is designed to hold multiple violation rows per report line. This makes it a diagnostic record set rather than a transactional control table: it does not itself block or approve an expense report, but provides the evidence trail that Payables uses to inform approvers and to drive expense report workflow outcomes.

Under heuristic Data Vault modeling, AP_POL_VIOLATIONS_ALL is classified as standalone. The mined foreign-key structure shows no enforced parent-child joins beyond its own composite identity, so it is best modeled as an independent satellite-like record set keyed by expense report context rather than as a hub or link. Implementers building a warehouse layer should treat it as an attribute-bearing detail table whose grain is report header, distribution line, and violation sequence.

Key Information Stored

The table contains 17 documented columns. Its composite primary key is AP_POL_VIOLATIONS_PK, defined on (REPORT_HEADER_ID, DISTRIBUTION_LINE_NUMBER, VIOLATION_NUMBER). A second unique index, AP_POL_VIOLATIONS_U1, carries the identical column list, so the documented business-key candidate and the surrogate identity coincide — there is no separate single-column surrogate key.

The most significant columns are:

Common Use Cases and Queries

The primary use cases are policy compliance reporting, approver review, and exception trending. Typical queries join back to the report header and distribution tables, filtering by operating unit and violation type.

  • Listing violations for a specific expense report:
    SELECT REPORT_HEADER_ID, DISTRIBUTION_LINE_NUMBER, VIOLATION_NUMBER, VIOLATION_TYPE, ALLOWABLE_AMOUNT, EXCEEDED_AMOUNT FROM AP.AP_POL_VIOLATIONS_ALL WHERE REPORT_HEADER_ID = :report_header_id ORDER BY DISTRIBUTION_LINE_NUMBER, VIOLATION_NUMBER;
  • Aggregating exceeded amounts by violation type for a period, using VIOLATION_DATE and ORG_ID to scope the analysis.
  • Identifying duplicate-expense exceptions by selecting rows where DUP_REPORT_HEADER_ID is populated.
  • Feeding an approval workflow so approvers can see entitlement breaches before authorizing payment.

Because ORG_ID is present, queries should respect MOAC predicates to avoid cross-operating-unit leakage.

Related Objects

Relationship metadata classifies the table as standalone, so joins are predominantly application-level rather than enforced foreign keys. The most significant related objects are:

  • AP_EXPENSE_REPORT_HEADERS_ALL — joined on REPORT_HEADER_ID to retrieve expense report context.
  • AP_EXPENSE_REPORT_LINES_ALL — joined on REPORT_HEADER_ID and DISTRIBUTION_LINE_NUMBER.
  • AP_EXPENSE_REPORT_DISTS_ALL — provides the distribution detail against which violations are recorded.
  • AP_POL_VIOLATIONS_PK / AP_POL_VIOLATIONS_U1 — the primary key constraint and unique index enforcing row uniqueness.
  • Payables Expense Report workflow and policy engine components — consume these rows during approval and audit.

Related expense report headers, lines, and distribution tables supply the report identity and line context referenced by DUP_REPORT_HEADER_ID, DUP_REPORT_LINE_ID, and DUP_DIST_LINE_NUMBER for duplicate-expense detection.