Results for “ap_oie_fuel_type_v”

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

Overview

AP_OIE_FUEL_TYPE_V is a read-only database view owned by the APPS schema in Oracle E-Business Suite, registered as VALID and classified under the Oracle Payables (AP) product family. Its purpose is narrow and well-defined: it surfaces the set of valid fuel type lookup values used by Oracle Internet Expenses (OIE) when employees enter fuel-related expense lines, such as mileage or fleet-card claims. Rather than exposing the entire lookup repository, the view filters the underlying lookup table to a single lookup type, OIE_FUEL_TYPE, and presents a clean, self-describing result set suitable for reporting, integration, and value-set style consumption.

Because Oracle Internet Expenses and Payables share the same APPS schema and lookup infrastructure, this view provides a stable, product-scoped interface for fuel type reference data. It is particularly useful to developers and analysts building expense analytics, extracts, or inbound validation routines, since the view abstracts away the LOOKUP_TYPE filter that would otherwise have to be repeated in every query.

Underlying Base Objects

The view text is defined as:

• SELECT LOOKUP_CODE, DISPLAYED_FIELD, DESCRIPTION FROM AP_LOOKUP_CODES WHERE LOOKUP_TYPE = 'OIE_FUEL_TYPE'

The documented base object is AP_LOOKUP_CODES, itself a view in the APPS schema that ultimately resolves to the Oracle Application Object Library lookup tables (FND_LOOKUP_VALUES / FND_LOOKUP_TYPES). A second referenced object is the FND_GLOBAL package, which is relevant because AP_LOOKUP_CODES is typically defined with a language or session-dependent restriction resolved through FND_GLOBAL.USERENV or LANGUAGE context. This means the row set returned can vary with the runtime language environment. The view exposes no base table of its own; it is purely a filtered projection over lookup reference data.

Key Columns

• LOOKUP_CODE — The internal, language-independent code stored on the expense line and used for validation and joins. This is the primary key values from the underlying lookup definition.
• DISPLAYED_FIELD — The user-facing value shown in the Internet Expenses fuel type list of values and rendered on forms and reports.
• DESCRIPTION — A longer descriptor associated with each lookup code, useful for reporting or for mapping codes to human-readable labels.

Notably, the view exposes only these three columns; it does not include effective dates, enabled flags, or language attributes directly. Those remain accessible through the parent AP_LOOKUP_CODES view or the underlying FND lookup tables when more control is required.

Common Use Cases and Queries

The most frequent scenario is populating a fuel type reference list in a downstream report, interface table, or external system. A typical query is:

• SELECT LOOKUP_CODE, DISPLAYED_FIELD, DESCRIPTION FROM APPS.AP_OIE_FUEL_TYPE_V ORDER BY DISPLAYED_FIELD;

Expense analysts use the same view to decode stored fuel codes on expense lines, joining it to AP_EXPENSE_REPORT_LINES_ALL or the OIE staging tables to produce readable fuel type descriptions. Integration developers reference it during inbound validation to confirm that a submitted fuel type value exists before loading. Because the view applies a fixed lookup type filter, it is safe to grant read access broadly without exposing unrelated lookup categories, making it a convenient and low-risk reference source across both 12.1.1 and 12.2.2 environments.