Search Results itemization_allowed

Overview

AP_WEB_EXP_TYPE_ITEM_V is a PL/SQL-backed view owned by the APPS schema in Oracle E-Business Suite (validated against 12.1.1 and 12.2.2). It is part of the Payables (AP) product and is used by the Internet Expenses (OIE / AP Web Expenses) module to present expense report parameter (expense type) definitions that are eligible for itemization. The view resolves the set of expense types available to a user for a given expense report, exposing only those categories for which itemization is permitted and, where applicable, only web-enabled entries.

Its role in EBS reporting and integration is to provide a stable, read-only interface over the configuration table AP_EXPENSE_REPORT_PARAMS, filtered and augmented by logic held in the AP_WEB_EXP_ITEM_UTIL package. Because the itemization decision and some report identifiers are computed through package function calls rather than plain column values, the view is not a simple projection of a single table; it is a purpose-built access path for itemization-aware expense type lookups.

Underlying Base Objects

The ETRM metadata documents two referenced base objects:

• AP_EXPENSE_REPORT_PARAMS (SYNONYM) — the primary source table, holding expense report parameters such as PARAMETER_ID, PROMPT, END_DATE, CATEGORY_CODE, and WEB_ENABLED_FLAG.
• AP_WEB_EXP_ITEM_UTIL (PACKAGE) — a utility package supplying the ITEMIZATION_ALLOWED function and the GET_REP_ID function referenced in the view text.

The view definition is a UNION of two SELECT statements against AP_EXPENSE_REPORT_PARAMS. Both branches exclude the PER_DIEM and MILEAGE category codes. The first branch selects parameters and calls AP_WEB_EXP_ITEM_UTIL.ITEMIZATION_ALLOWED(PARAMETER_ID) for the itemization flag, while selecting EXPENSE_REPORT_ID directly. The second branch computes EXPENSE_REPORT_ID via AP_WEB_EXP_ITEM_UTIL.GET_REP_ID and restricts results to rows where WEB_ENABLED_FLAG = 'Y'. This structure means the view blends static configuration data with dynamically derived values, so performance and results depend on the underlying functions.

Key Columns

• PARAMETER_ID — surrogate identifier for the expense report parameter (expense type) row; the key passed into ITEMIZATION_ALLOWED.
• EXPENSE_REPORT_ID — identifier linking the parameter to an expense report; populated directly in the first branch and via GET_REP_ID in the second.
• PROMPT — the display label presented to the user for the expense type.
• END_DATE — the effective end (inactive) date of the parameter; used to determine current validity.
• ITEMIZATION_ALLOWED — computed flag indicating whether the expense type may be itemized.
• WEB_ENABLED_FLAG — indicates whether the parameter is available for web (Internet Expenses) entry.

Common Use Cases and Queries

Typical uses include determining which expense types a user may select or itemize on a web expense report, and validating itemization eligibility during report entry or approval.

SELECT parameter_id, expense_report_id, prompt,
       end_date, itemization_allowed, web_enabled_flag
FROM   apps.ap_web_exp_type_item_v
WHERE  itemization_allowed = 'Y'
AND    (end_date IS NULL OR end_date > SYSDATE);

To retrieve web-enabled expense types for a specific report:

SELECT prompt, itemization_allowed
FROM   apps.ap_web_exp_type_item_v
WHERE  expense_report_id = :p_expense_report_id
AND    web_enabled_flag = 'Y';

Because the view invokes package functions per row, queries benefit from filtering on EXPENSE_REPORT_ID or WEB_ENABLED_FLAG to reduce function calls. It is intended for read access only and should not be used as a target for DML.