Search Results icx_ap_expense_reports_v




Overview
Explore in AI Chat

Overview

APPS.ICX_AP_EXPENSE_REPORTS_V is a database view owned by the APPS schema and delivered as part of the Oracle iProcurement (ICX) product family, with supporting dependencies on Oracle Payables (AP) and Internet Expenses. In Oracle E-Business Suite 12.1.1 and 12.2.2, this view exposes the header-level information of employee expense reports, presenting them in a consolidated, reporting-friendly format that mirrors the structure of supplier invoices in the Payables model.

Expense reports are stored internally as invoices in AP_INVOICES and AP_EXPENSE_REPORT_HEADERS. The view overlays that transactional data with payment schedule amounts, currency-formatted values, vendor and vendor site details, employee identifiers, and lookup-driven descriptive fields. Its role is primarily presentational and integration-oriented: it provides iProcurement and self-service expense functionality with a stable, denormalized projection of expense report headers without requiring callers to join multiple base tables or invoke currency-formatting logic directly. Because display values such as formatted amounts, payment status, invoice type, and approval indicators are computed inside the view, downstream pages and reports receive human-readable results consistently across the EBS instance.

Underlying Base Objects

The view is defined over a combination of synonym-backed base tables, views, and PL/SQL packages. Documented referenced objects include AP_EXPENSE_REPORT_HEADERS, AP_INVOICES, AP_PAYMENT_SCHEDULES, AP_LOOKUP_CODES (view), PER_ALL_PEOPLE_F, PO_VENDORS (view), and PO_VENDOR_SITES (view). The core transactional data is driven from AP_INVOICES (aliased AI) and linked to payment schedules in AP_PAYMENT_SCHEDULES (aliased APS), which supply due dates, gross amounts, amount remaining, discount dates, and discount amounts. Employee identity is resolved through PER_ALL_PEOPLE_F (aliased P), while vendor and vendor site attributes come from PO_VENDORS and PO_VENDOR_SITES.

Functional logic is embedded through several PL/SQL packages: FND_CURRENCY.GET_FORMAT_MASK applies currency formatting masks, ICX_AP_INVOICES_PKG.GET_AMOUNT_WITHHELD and GET_PO_NUMBER_LIST retrieve withheld amounts and associated purchase order numbers, ICX_AP_INVOICE_PAYMENTS_PKG.GET_PAID_BY_LIST resolves payment references, and AP_WEB_FND_LOOKUPS_PKG.GETYESNOMEANING translates yes/no indicators. Lookup display values for invoice type and payment status are supplied via AP_LOOKUP_CODES.

Key Columns

Common Use Cases and Queries

Typical uses include expense report listing pages in iProcurement and Internet Expenses, self-service reporting, and outbound integration feeds that require formatted header data. The view is frequently queried by employee, status, or date range to display outstanding or historical expense reports. A representative query follows:

SELECT invoice_num,
       description,
       employee_id,
       invoice_amount,
       amount_remaining,
       payment_status,
       due_date
FROM   apps.icx_ap_expense_reports_v
WHERE  employee_id = :p_employee_id
ORDER  BY invoice_date DESC;

Because formatting and lookups are resolved internally, external reports and interfaces can consume the view directly without reimplementing currency masks or approval translations, ensuring consistent presentation across EBS 12.1.1 and 12.2.2.