Results for “ap_oie_audit_types_v”

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

Overview

The view AP_OIE_AUDIT_TYPES_V is an Oracle E-Business Suite database object owned by the APPS schema and validated in both Oracle EBS 12.1.1 and 12.2.2. It resides in the Oracle Payables (AP) product family and serves as a filtered presentation layer over the Oracle Internet Expenses (OIE) audit type lookup data. The name reflects its purpose: it exposes the set of valid audit types configured for the Oracle Internet Expenses module, which governs how expense reports are audited, whether by policy validation, corporate card reconciliation, or other controls.

In EBS reporting and integration contexts, the view functions as a lightweight, read-only reference source. Rather than querying the underlying AP_LOOKUP_CODES view with a hard-coded lookup type, developers, report builders, and integration specialists can select directly from AP_OIE_AUDIT_TYPES_V to obtain only the audit type values relevant to Internet Expenses. This encapsulation simplifies SQL and ensures consistency across custom reports, Oracle Discoverer workbooks, OBIEE repositories, and third-party interfaces that need to resolve a stored audit type code into a user-facing description.

Underlying Base Objects

Per the documented ETRM metadata, the view is defined over two referenced base objects:

• AP_LOOKUP_CODES (VIEW) — The primary data source. The view definition selects LOOKUP_CODE, DISPLAYED_FIELD, and DESCRIPTION from AP_LOOKUP_CODES restricted by the predicate LOOKUP_TYPE = 'OIE_AUDIT_TYPES'. This restriction is the essential logic of the view, isolating the Internet Expenses audit type lookup values from the broader Payables lookup collection.
• FND_GLOBAL (PACKAGE) — Referenced for session context resolution. Oracle EBS lookup views commonly invoke FND_GLOBAL to obtain the effective user, responsibility, and language so that the correct displayed values and descriptions are returned for the active session and localization.

Because the view sits atop a lookup view rather than directly on the FND_LOOKUP_VALUES or AP_LOOKUP_CODES base tables, its content is maintained through the standard Oracle lookup maintenance forms. Values are seeded or added by administrators when configuring Internet Expenses audit behavior, and the view simply surfaces them.

Key Columns

• LOOKUP_CODE — The internal code identifying the audit type. This is the value typically stored on expense report transaction records and referenced programmatically by validation logic.
• DISPLAYED_FIELD — The user-visible label associated with the lookup code. Reports and forms use this column when presentation of a human-readable audit type is required.
• DESCRIPTION — Additional explanatory text describing the audit type, useful for documentation, help text, or analytical classification.

All three columns surface directly from AP_LOOKUP_CODES; no transformation or computation is applied beyond the lookup type filter.

Common Use Cases and Queries

The view is most frequently used to populate selection lists, join to expense report or audit results data, and produce reference listings for configuration review.

Listing all configured Internet Expenses audit types:

• SELECT lookup_code, displayed_field, description FROM apps.ap_oie_audit_types_v ORDER BY displayed_field;

Resolving a stored code to its displayed label:

• SELECT displayed_field FROM apps.ap_oie_audit_types_v WHERE lookup_code = :audit_type_code;

Joining to audit results for a descriptive report:

• SELECT t.lookup_code, t.displayed_field, a.expense_report_id FROM apps.ap_oie_audit_types_v t, apps.ap_expense_audit_results_all a WHERE t.lookup_code = a.audit_type;

Typical consumers include custom Payables and Expenses reports, OBIEE or BI Publisher data models, Discoverer workbooks, and integration extracts that must validate audit type codes before loading data into downstream systems. Because the view is read-only and maintained by Oracle, it is stable and safe to reference, though administrators should confirm that any custom code does not hard-code values that may be extended by new lookup entries.