Search Results per_diem




Overview
Explore in AI Chat

Overview

APPS.AP_WEB_EXP_TYPE_ITEM_V is an Oracle E-Business Suite view owned by the APPS schema that exposes expense report parameter definitions used by the Oracle Internet Expenses (OIE) web application. Its principal function is to present the itemization parameters configured for expense report types so that the web-based expense entry pages can present the correct prompts, enforce effective dates, and determine whether a given parameter supports itemization and whether it is available to web users. The view is therefore a configuration-facing construct rather than a transactional reporting object: it surfaces the metadata that governs how expense lines are captured and validated in the self-service expense workflow.

The view is relevant to releases 12.1.1 and 12.2.2 of Oracle EBS, where Oracle Internet Expenses relies on this structure to drive the expense template rendering for the web UI. The web_enabled_flag column, which appears explicitly in the view text, is the attribute most commonly queried by implementers and technical consultants when they need to identify which expense parameters are exposed to the web application.

Underlying Base Objects

The documented base objects referenced by the view are the synonym AP_EXPENSE_REPORT_PARAMS and the package AP_WEB_EXP_ITEM_UTIL.

  • AP_EXPENSE_REPORT_PARAMS — the table (referenced through its APPS synonym) that stores the definition of every expense report parameter, including the parameter identifier, the associated expense report, the display prompt, the effective end date, the category code, and the web-enabled flag. Both branches of the view's UNION query select from this table.
  • AP_WEB_EXP_ITEM_UTIL — a PL/SQL package whose functions are invoked directly inside the view definition. The function ITEMIZATION_ALLOWED(parameter_id) is called in the select list of both UNION branches to compute the itemization indicator, and GET_REP_ID is used in the second branch to derive the expense report identifier. This makes the view partly dependent on PL/SQL logic at query time.

The view is built as a UNION of two SELECT statements. The first branch returns all parameters whose category code is not 'PER_DIEM' or 'MILEAGE'. The second branch returns parameters with a category code outside those same exclusions and with web_enabled_flag = 'Y'. Both branches project the same six columns in the same order, satisfying UNION column compatibility.

Key Columns

  • PARAMETER_ID — the unique identifier of the expense report parameter; also the input to the itemization function.
  • EXPENSE_REPORT_ID — in the first branch this is the stored column value; in the second branch it is supplied by AP_WEB_EXP_ITEM_UTIL.GET_REP_ID, allowing the report identifier to be resolved contextually.
  • PROMPT — the label displayed to the user for the parameter in the web expense entry pages.
  • END_DATE — the effective end date of the parameter, used to determine whether the parameter is currently active.
  • ITEMIZATION_ALLOWED (computed) — the value returned by AP_WEB_EXP_ITEM_UTIL.ITEMIZATION_ALLOWED(parameter_id), indicating whether expense lines created against this parameter may be itemized.
  • WEB_ENABLED_FLAG — the flag indicating whether the parameter is exposed to the web application. Because the second UNION branch filters on this column, rows returned from that branch are always 'Y'.

Common Use Cases and Queries

The view is typically queried when diagnosing which expense parameters are visible in the web expense entry flow, when verifying itemization behavior, or when validating configuration after a patch or upgrade. A representative query lists the web-enabled parameters for a given report:

SELECT parameter_id, expense_report_id, prompt, end_date, web_enabled_flag
FROM ap_web_exp_type_item_v
WHERE web_enabled_flag = 'Y'
ORDER BY expense_report_id, parameter_id;

Because the view invokes package functions in its select list, queries against it execute PL/SQL for each row returned and cannot be tuned through conventional index strategies on the computed columns. When only the flag is required, querying AP_EXPENSE_REPORT_PARAMS directly filters more efficiently. The view should nevertheless be used whenever the itemization determination must match exactly what Oracle Internet Expenses applies at runtime.