Search Results ap_pol_violations_u1

Overview

AP.AP_POL_VIOLATIONS_ALL is an Oracle E-Business Suite Payables table that stores policy violation details for expense report distribution lines. It records the type of violation raised against an individual expense receipt line and the allowable amount permitted under company policy at the time the violation was detected. Because the table carries an ORG_ID column and the ETRM documentation explicitly states that the object is organization specific, it is a multi-org enabled table and rows are partitioned logically by operating unit, with the _ALL suffix denoting the presence of the org identifier rather than a partitioned physical segment.

From a data modeling perspective, ETRM classifies this object heuristically as standalone, meaning that no foreign key dependencies were mined from its physical structure. In Data Vault terms the table is best modeled as a satellite attached to the expense report distribution line hub, since it captures descriptive policy attributes (violation type, allowable amount, exceeded amount, violation date) tied to a business key composed of report header, distribution line, and violation number. It should not be treated as a hub or link in its own right, because its grain is entirely dependent on the parent expense report line.

Key Information Stored

The unique index AP_POL_VIOLATIONS_U1, which the user searched for, is defined on the columns REPORT_HEADER_ID, DISTRIBUTION_LINE_NUMBER, and VIOLATION_NUMBER. These three columns also form the primary key AP_POL_VIOLATIONS_PK, so in this table the surrogate-free composite key and the business key coincide; there is no separate generated identifier.

• REPORT_HEADER_ID – identifies the expense report header to which the violation belongs.
• DISTRIBUTION_LINE_NUMBER – the expense report distribution line, corresponding to an individual receipt line.
• VIOLATION_NUMBER – sequence number allowing multiple violations to exist against one distribution line.
• VIOLATION_TYPE – descriptive classification of the policy breach (for example, exceeding a category limit).
• ALLOWABLE_AMOUNT – the amount permitted by company policy, expressed in the receipt currency.
• FUNC_CURRENCY_ALLOWABLE_AMT – the same allowable limit converted to the ledger functional currency.
• EXCEEDED_AMOUNT – the portion of the expense exceeding the allowable limit.
• VIOLATION_DATE – the date on which the violation occurred.
• ORG_ID – the operating unit that owns the row, enforcing multi-org security.
• DUP_REPORT_HEADER_ID, DUP_REPORT_LINE_ID, DUP_DIST_LINE_NUMBER – pointers used when the violating line duplicates an existing expense report line.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN – standard WHO audit columns.

The table resides in the APPS_TS_TX_DATA tablespace while its unique index is stored in APPS_TS_TX_IDX, a separation typical of high-volume transactional data and its supporting index.

Common Use Cases and Queries

The principal reporting requirement is to surface all policy violations for a given expense report so that approvers and auditors can review them. A typical query selects violation details by header:

• 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 = :p_header_id ORDER BY distribution_line_number, violation_number;

Because the table is org specific, any query executed from a multi-org enabled session should restrict by ORG_ID, or rely on the MOAC views that automatically append the operating unit predicate. Common analytical uses include aggregating exceeded amounts by violation type to identify recurring policy breaches, comparing the functional currency allowable amount against the entered amount for cross-currency expense reports, and joining to expense report distribution lines to reconstruct the full receipt context for a violation.

Related Objects

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

• AP_EXPENSE_REPORT_HEADERS_ALL – joined on REPORT_HEADER_ID to obtain report-level attributes such as preparer, status, and dates.
• AP_EXPENSE_REPORT_LINES_ALL – joined on REPORT_HEADER_ID and DISTRIBUTION_LINE_NUMBER to obtain the expense line detail.
• AP_EXPENSE_REPORT_DISTS_ALL – joined on the same distribution line key to reconcile accounting distributions for the violating line.
• AP_POL_VIOLATIONS – the org-specific view over this table used for reporting in a single operating unit context.
• FND_USER – joined on CREATED_BY and LAST_UPDATED_BY to resolve user names for audit reporting.
• FND_LOGINS – joined on LAST_UPDATE_LOGIN for session-level audit tracing.
• HR_OPERATING_UNITS – joined on ORG_ID to resolve the operating unit name.

No foreign key constraints were documented for this object, so joins above are semantic rather than enforced at the database level, and referential integrity is maintained by the expense report policy validation logic within the Payables application.