Results for “apbv_pol_violations”

14 results




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

Overview

APBV_POL_VIOLATIONS is a business (secured) view owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It belongs to the Oracle Payables (AP) product family and exposes expense policy violation data captured during invoice and expense report processing. The view presents the results of the Payables policy enforcement engine, which compares submitted expense lines against the allowable limits defined in expense policy setups and records any amounts that breach those limits.

The primary purpose of the view is to provide a reporting- and integration-friendly projection of violation records without requiring direct access to the underlying transactional table. Because it is a business view, it participates in Oracle's Multi-Org security model: row-level access is filtered through the ORG_ID operating unit, and the view is defined with the WITH READ ONLY clause, preventing DML through the view. The view is marked VALID in the ETRM metadata, confirming that its definition resolves cleanly against the current database object structure.

For users searching on the term exceeded_amount, this view is the relevant object: EXCEEDED_AMOUNT is one of the columns projected by the view and represents the monetary value by which a given expense distribution line exceeded its allowable policy limit.

Underlying Base Objects

The view is defined over a single documented base object, AP_POL_VIOLATIONS_ALL, which is referenced via a synonym. The _ALL suffix indicates that the base table stores violation rows for all operating units, with each row carrying an ORG_ID. The view text selects from this table using the alias APVA and applies the Oracle Multi-Org security predicate '_SEC:APVA.ORG_ID' IS NOT NULL, which is substituted at runtime with the set of operating units accessible to the current responsibility.

Because the view performs a simple projection with no joins, aggregation, or filtering beyond Multi-Org security, its column set mirrors the base table exactly. The restriction to a read-only view means that any correction or purge of violation data must be performed against AP_POL_VIOLATIONS_ALL itself, subject to the appropriate privileges.

Key Columns

  • REPORT_HEADER_ID — Identifier linking the violation to the expense report or invoice header under which the offending line was submitted.
  • DISTRIBUTION_LINE_NUMBER — The distribution line within the report to which the violation applies.
  • VIOLATION_NUMBER — Sequence number uniquely identifying the violation record within the report context.
  • VIOLATION_TYPE — Classifies the nature of the policy breach (for example, an exceeded allowable amount).
  • ALLOWABLE_AMOUNT — The policy limit amount permitted for the line, expressed in the policy currency.
  • FUNC_CURRENCY_ALLOWABLE_AMT — The allowable amount converted into the functional currency of the operating unit.
  • EXCEEDED_AMOUNT — The amount by which the submitted expense exceeded the allowable limit; this is the value most commonly queried for policy audit and reimbursement adjustment.
  • VIOLATION_DATE — The date on which the violation was recorded.
  • ORG_ID — Operating unit identifier, enforcing Multi-Org security partitioning.
  • Standard audit columns CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, and LAST_UPDATE_DATE — Track record creation and modification.

Common Use Cases and Queries

Typical uses include policy compliance reporting, reimbursement adjustment review, and upstream integration feeds delivering violation data to audit or analytics systems.

List all violations for the current operating unit:

SELECT report_header_id, distribution_line_number, violation_type,
       allowable_amount, exceeded_amount, violation_date
FROM   apps.apbv_pol_violations
ORDER  BY report_header_id, distribution_line_number;

Identify lines where the exceeded amount is material:

SELECT report_header_id, distribution_line_number,
       allowable_amount, func_currency_allowable_amt, exceeded_amount
FROM   apps.apbv_pol_violations
WHERE  exceeded_amount > 1000
ORDER  BY exceeded_amount DESC;

Summarize total exceeded amounts by report:

SELECT report_header_id, SUM(exceeded_amount) total_exceeded
FROM   apps.apbv_pol_violations
GROUP  BY report_header_id;

Because Multi-Org security is embedded in the view definition, these queries return only data for operating units accessible to the connecting responsibility; no additional ORG_ID predicate is required.