Search Results report_number_field




Overview

APPS.AP_EXPENSE_REPORT_HISTORY_V is a reporting view in Oracle E-Business Suite (available in both 12.1.1 and 12.2.2) that consolidates the history of employee expense reports by joining expense report header information with their corresponding Oracle Payables invoices. The view blends data from the expense reporting module (Oracle Internet Expenses) and the payables module, giving a unified record of an expense report, its reimbursable amounts, invoice details, payment status, and currency-formatted totals. It is primarily intended for self-service and administrative reporting where users need to trace an expense report through to its payable invoice.

Because it surfaces presentation-oriented fields alongside raw identifiers, the view fits neatly into Oracle EBS's model of exposing declarative flags to the user interface layer. The REPORT_NUMBER_FIELD column, for instance, returns either ReportNumberEnabled or ReportNumberDisabled, and is exactly what a search on "report_number_field" would locate. These decorative columns do not store business data; they instruct the consuming UI or report whether a given feature, such as displaying a report number or an expense-lines link, is applicable for the current record.

Underlying Base Objects

The view is defined over a mix of base tables, synonyms, packages, and other views in the APPS schema. Documented referenced objects include:

Key Columns

Common Use Cases and Queries

Typical uses include auditing the status of submitted expense reports, reconciling reimbursements against payable invoices, and driving self-service pages that conditionally show the report number or expense-line image link.

SELECT report_header_id,
       invoice_num,
       full_name,
       status,
       invoice_amount,
       report_number_field
FROM   apps.ap_expense_report_history_v
WHERE  employee_id = :p_employee_id;

To locate records where the report number should be displayed:

SELECT invoice_num, report_number_field
FROM   apps.ap_expense_report_history_v
WHERE  report_number_field = 'ReportNumberEnabled';

Because the view applies package logic and currency masks, it should be queried rather than replicated, and performance is best where filters on employee or report identifiers are applied.