Results for “ap_oie_pol_violation_types_v”

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

Overview

AP_OIE_POL_VIOLATION_TYPES_V is a read-only view owned by the APPS schema in Oracle E-Business Suite, registered as VALID and associated with the Payables (AP) product family. Its purpose is to expose the set of Oracle Internet Expenses (OIE) policy violation type codes that the Payables-side policy engine, and related expense-auditing components, use to categorize exceptions raised against expense reports. The view is a thin, stable projection over the standard Oracle Applications lookup mechanism, restricting the generic lookup infrastructure to a single lookup type, OIE_POL_VIOLATION_TYPES. Because policy violation categories are administrative reference data rather than transactional data, this view is typically consumed for validation, display, and reporting rather than for data entry.

The object is documented in ETRM at both 12.1.1 and 12.2.2, with identical column structure and definition, so it carries forward unchanged between those releases.

Underlying Base Objects

ETRM documents two referenced base objects: AP_LOOKUP_CODES (itself a view) and the FND_GLOBAL package. The view text supplied in the metadata is:

SELECT LOOKUP_CODE, DISPLAYED_FIELD, DESCRIPTION
FROM AP_LOOKUP_CODES
WHERE LOOKUP_TYPE = 'OIE_POL_VIOLATION_TYPES'

AP_LOOKUP_CODES is the Payables-owned view that resolves lookup values and their effective-dated translations, ultimately deriving from the FND_LOOKUP_VALUES / FND_LOOKUP_TYPES foundation tables and applying FND_GLOBAL security and language context. FND_GLOBAL supplies session attributes such as the current language (FND_GLOBAL.LANGUAGE) used to return the appropriate displayed value. The net effect is that AP_OIE_POL_VIOLATION_TYPES_V behaves as a filtered, Payables-branded enumeration of violation categories, isolated from other OIE policy lookup types (for example violation actions or statuses).

Key Columns

• LOOKUP_CODE — The internal, language-independent code identifying the policy violation type. This is the value stored on transaction or audit records and is the join key for downstream queries.
• DISPLAYED_FIELD — The user-facing (translatable) label for the violation type, resolved for the session language. This is the value suited to reports, LOVs, and notifications.
• DESCRIPTION — An optional longer explanation of the violation type, provided for clarification where the short displayed value is insufficient.

Because the view filters solely on LOOKUP_TYPE, no additional enabled/disabled column is projected; callers relying on active-status filtering should join to the wider lookup views if that distinction matters.

Common Use Cases and Queries

The view is used to decode referenced lookup codes into readable labels, to drive LOVs and validation lists, and to support reconciliation of expense-audit exceptions during period close. Typical patterns include:

• Populating a violation-type selection list on a custom audit form or OAF page.
• Decoding stored codes on expense-audit extract reports.
• Validating values passed into custom integration interfaces.

Sample query to enumerate configured violation types:

SELECT lookup_code, displayed_field, description
FROM   apps.ap_oie_pol_violation_types_v
ORDER BY displayed_field;

Sample join to decode codes held on a custom audit table:

SELECT a.expense_report_id, a.violation_code,
       v.displayed_field
FROM   apps.xx_audit_exceptions a,
       apps.ap_oie_pol_violation_types_v v
WHERE  a.violation_code = v.lookup_code;

Administrators should note that the underlying values are maintained through the standard Oracle Applications lookup maintenance forms for type OIE_POL_VIOLATION_TYPES; the view itself is not directly updatable.