Results for “ap_expense_types_v”

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

Overview

AP_EXPENSE_TYPES_V is a PL/SQL view owned by the APPS schema within the Oracle Payables (AP) product family. Its documented status is VALID, and it is supplied as a standard Oracle E-Business Suite database object. The view exists primarily to support Oracle Internet Expenses (OIE), where the value set that drives the Expense Types list on the expense entry Details page is defined against this view. Because the Expense Type field in the Details page is a validated flexfield-style list of values, the view supplies the selectable expense types and their user-facing prompts to the OIE user interface.

The view is therefore best understood as a presentation and validation layer rather than a transactional table. It does not store expense data; instead, it exposes a filtered, de-duplicated projection of expense report parameters configured in the underlying Payables setup. This role makes it relevant both to end users entering expense reports and to technical consultants building reports, interfaces, or extensions that need the same list of active expense types presented to users in OIE.

Underlying Base Objects

According to the documented view text, AP_EXPENSE_TYPES_V is defined over a single referenced base object: AP_EXPENSE_REPORT_PARAMS, accessed through a synonym in the APPS schema. The view is a simple SELECT DISTINCT statement over that table, projecting a defined set of columns. Because there is only one base table, the view is a straightforward denormalized projection with no joins, unions, or aggregations beyond the DISTINCT keyword used to remove duplicate rows.

The DISTINCT clause is significant: AP_EXPENSE_REPORT_PARAMS can contain multiple parameter rows that resolve to identical combinations of the projected columns, and the view collapses those duplicates so the Internet Expenses value set returns each expense type once. No filtering by date or enabled flag is documented in the view text itself, so consumers should be prepared to apply their own filters on END_DATE or WEB_ENABLED_FLAG if only currently active, web-visible expense types are required.

Key Columns

• PARAMETER_ID — Identifier of the underlying expense report parameter row; the natural primary key inherited from AP_EXPENSE_REPORT_PARAMS.
• WEB_PROMPT — The prompt displayed to users, derived as NVL(WEB_FRIENDLY_PROMPT, PROMPT). It falls back to the standard PROMPT when no web-friendly alternative is configured.
• PROMPT — The base name of the expense type parameter as defined in Payables setup.
• EXPENSE_REPORT_ID — The expense report definition to which the parameter belongs. This column is the target of the user's search for "expense_report_id" and links the expense type back to its owning report template.
• WEB_ENABLED_FLAG — Indicates whether the expense type is exposed on the web (Internet Expenses) interface.
• PA_EXPENDITURE_TYPE — The Projects (PA) expenditure type associated with the expense type, used for costing and expenditure categorization.
• CATEGORY_CODE — The expense category classification applied to the type.
• END_DATE — Effective end date of the parameter; a NULL or future value generally indicates the row remains active.

Common Use Cases and Queries

The most common use of this view is to reproduce the Internet Expenses Expense Type list of values in custom reports, extensions, or validation logic. Consultants also query it to inspect which expense types are web-enabled for a given expense report definition, and to join expense lines back to the expenditure type and category used for accounting.

A typical query listing active, web-enabled expense types for a specific expense report is:

• SELECT parameter_id, web_prompt, pa_expenditure_type, category_code FROM apps.ap_expense_types_v WHERE expense_report_id = :p_report_id AND web_enabled_flag = 'Y' AND (end_date IS NULL OR end_date > SYSDATE) ORDER BY web_prompt;

To resolve an expenditure type from a displayed prompt, the view can be joined on WEB_PROMPT or PROMPT. Because the source table is AP_EXPENSE_REPORT_PARAMS, any report that must align with OIE expense entry behavior should read from AP_EXPENSE_TYPES_V rather than querying the base table directly, ensuring the same de-duplication and prompt fallback logic applied by the seeded value set.