Results for “ap_pol_violations_v”

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

Overview

AP_POL_VIOLATIONS_V is a Payables (AP) reporting view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes the results of Oracle Payables' policy (POL) validation performed on invoice distributions, and it is part of the infrastructure that underpins the Invoice Validation workflow and the associated hold resolution screens. The acronym "POL" designates the policy violation checks that a Payables implementation can configure — for example, maximum allowable distribution amounts or item-level spending limits. When a distribution breaches a configured policy, Payables records a violation in the base table and, optionally, records the duplicate report header, line, and distribution-line reference that identifies the second entry responsible for a duplicate condition.

The view's practical significance lies in the column DUP_DIST_LINE_NUMBER. Implementation consultants and support analysts who search for the term dup_dist_line_number are typically investigating a duplicate invoice-line or distribution-line condition surfaced during validation, and this view is the documented join point between the violation record and the duplicate distribution reference. Because the object is a view rather than a table, it can be queried read-only without affecting transactional state and is suitable for ad-hoc diagnostics, custom reports, and integration extracts.

Underlying Base Objects

Per the documented view text, AP_POL_VIOLATIONS_V is defined over three referenced base objects:

• AP_POL_VIOLATIONS — the synonym that resolves to the underlying violation table, aliased as AV. This is the primary source of violation rows, including report header, distribution line, violation number, violation type, allowable amount, and the duplicate reference columns.
• AP_LOOKUP_CODES — a view over the Payables lookup repository, aliased as LC. The join restricts the lookup type to OIE_POL_VIOLATION_TYPES, and the violation type code on the violation row is matched to the lookup code to retrieve the user-facing description.
• FND_GLOBAL — the standard Oracle Application Object Library package used for session context (such as responsibility and user identifier). It is referenced in the view metadata but does not appear in the join clause of the published view text.

The join predicate between AP_POL_VIOLATIONS and AP_LOOKUP_CODES is an equality between AV.VIOLATION_TYPE and LC.LOOKUP_CODE, constrained by LC.LOOKUP_TYPE = 'OIE_POL_VIOLATION_TYPES'. This is an inner join, so violations whose type code is not defined in that lookup type are not returned by the view.

Key Columns

• REPORT_HEADER_ID — identifies the policy violation report (or exception report) header to which the violation belongs.
• DISTRIBUTION_LINE_NUMBER — the distribution line on the invoice that triggered the violation.
• VIOLATION_NUMBER — the sequential number of the violation within the report.
• VIOLATION_TYPE — the code identifying the type of policy breach; joins to AP_LOOKUP_CODES.
• ALLOWABLE_AMOUNT — the threshold amount permitted by the policy; a violation occurs when the distribution exceeds this value.
• DISPLAYED_FIELD — the lookup meaning/description used to present the violation type to the user.
• DUP_REPORT_HEADER_ID — header identifier of the duplicate exception report, if the violation results from a duplicate.
• DUP_REPORT_LINE_ID — line identifier within the duplicate exception report.
• DUP_DIST_LINE_NUMBER — the distribution line number of the suspected duplicate entry, enabling the analyst to compare the original and duplicate distributions directly.

Common Use Cases and Queries

Typical usage is investigative: listing all violations for a report, inspecting duplicate violations only, or mapping violation types to their descriptive meanings.

• All violations for a given report: SELECT DISTRIBUTION_LINE_NUMBER, VIOLATION_NUMBER, VIOLATION_TYPE, DISPLAYED_FIELD, ALLOWABLE_AMOUNT FROM AP_POL_VIOLATIONS_V WHERE REPORT_HEADER_ID = :p_header_id ORDER BY VIOLATION_NUMBER;
• Duplicate-related violations: SELECT DISTRIBUTION_LINE_NUMBER, DUP_DIST_LINE_NUMBER, DUP_REPORT_HEADER_ID, DUP_REPORT_LINE_ID FROM AP_POL_VIOLATIONS_V WHERE DUP_DIST_LINE_NUMBER IS NOT NULL;
• Count by violation type: SELECT DISPLAYED_FIELD, COUNT(*) FROM AP_POL_VIOLATIONS_V GROUP BY DISPLAYED_FIELD;

Because AP_LOOKUP_CODES is joined internally, the DISPLAYED_FIELD column already supplies a readable label, so no additional lookup resolution is normally required. Users should note that the view does not expose invoice number or supplier directly; those attributes are obtained by joining the report header or distribution identifiers to the appropriate Payables tables.