Search Results icx_ap_expense_lines_v




Overview
Explore in AI Chat

Overview

ICX_AP_EXPENSE_LINES_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, shipped as part of the ICX (Oracle iProcurement) product family. The view is described in the ETRM repository as the "Employee Expense Reports Line View" and is registered with a status of VALID in both 12.1.1 and 12.2.2 environments. Its primary purpose is to expose expense report distribution lines — that is, the individual expense lines flowing into an AP invoice — in a form suitable for display and processing within the iProcurement self-service expense entry and review flows.

Functionally, the view resolves the gap between the normalized Payables expense distribution model and the flattened, presentation-oriented structure that Internet Computing Architecture (ICX) pages require. Rather than joining AP tables directly, ICX pages and related reports query this view, which supplies both raw identifiers (invoice ID, distribution line number) and pre-formatted, currency-masked monetary amounts. It also injects security and descriptive enrichment through lookups, project and task segments, grants award numbers, and workforce management prompts.

Underlying Base Objects

Per the ETRM 12.2.2 metadata, ICX_AP_EXPENSE_LINES_V is defined over the following documented base objects, most of which are APPS synonyms over the corresponding ERP tables:

The view text confirms an inner join between AP_INVOICES and AP_INVOICE_DISTRIBUTIONS on INVOICE_ID, with an outer join to AP_EXPENSE_REPORT_PARAMS via WEB_PARAMETER_ID, plus additional joins to project, task, and award sources. A filter excludes credit-card reversal lines (CC_REVERSAL_FLAG <> 'Y').

Key Columns

The view exposes both identifiers and formatted display values. Notable columns include:

Common Use Cases and Queries

Typical use cases include: rendering the expense line detail region in iProcurement expense pages, building custom operational reports of employee expense lines, feeding downstream reconciliation or audit extracts, and joining to AP invoices for approval analysis. Because the view returns formatted monetary strings, it is frequently used directly in BI Publisher and Discoverer reports without additional formatting.

A simple query retrieving the primary expense line attributes for an invoice might resemble:

  • SELECT REPORT_FOREIGN_KEY, DISTRIBUTION_LINE_NUMBER, EXPENSE_TYPE, AMOUNT, DAYS, SEGMENT1, TASK_NUMBER, AWARD_NUMBER FROM apps.icx_ap_expense_lines_v WHERE REPORT_FOREIGN_KEY = :p_invoice_id ORDER BY DISTRIBUTION_LINE_NUMBER;

To list lines with missing receipts for a date range:

  • SELECT REPORT_FOREIGN_KEY, EXPENSE_TYPE, AMOUNT, START_EXPENSE_DATE FROM apps.icx_ap_expense_lines_v WHERE RECEIPT_MISSING_FLAG = 'Y' AND START_EXPENSE_DATE BETWEEN :p_from AND :p_to;

Because the view is a thin reporting layer, joins to HR or project tables should generally be performed via the exposed identifiers (invoice ID, segment, task) rather than re-deriving them. Standard APPS security through HR_SECURITY governs which expense lines a user can retrieve, so custom code querying this view inherits the same row-level restrictions as iProcurement screens.