Results for “apbv_expense_report_headers”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

APBV_EXPENSE_REPORT_HEADERS is an Oracle Payables (AP) view owned by the APPS schema and exposed through the E-Business Suite Technical Reference Manual (ETRM) for releases 12.1.1 and 12.2.2. It presents header-level information for Oracle Internet Expenses (OIE) expense reports, which are employee-submitted reimbursement requests processed through Oracle Payables and Oracle Workflow. The view is a reporting and integration façade over the expense report header table, joining the stored header columns with values derived at runtime from the AP_WEB_OA_ACTIVE_PKG package, such as the calculated expense status code. Because it consolidates identity, currency, approval, prepayment, and payment-related attributes onto a single row per report header, the view is commonly used by custom reports, interfaces, and inquiry forms that need a denormalized, read-only picture of an expense report without navigating the base table's full column set.

Underlying Base Objects

According to the documented ETRM metadata, APBV_EXPENSE_REPORT_HEADERS is defined over two referenced objects:

• AP_EXPENSE_REPORT_HEADERS_ALL (referenced via a synonym) — the primary base table storing one row per expense report header. It supplies nearly all columns surfaced by the view.
• AP_WEB_OA_ACTIVE_PKG (PL/SQL package) — invoked inline in the view text through the call AP_WEB_OA_ACTIVE_PKG.GETREPORTSTATUSCODE, which derives the expense status code when AERHA.EXPENSE_STATUS_CODE is null.

The view aliases the header table as AERHA and carries the descriptive flexfield reference '_DF:SQLAP:AP_EXPENSE_REPORT_HEADERS:AERHA', confirming the DFF context originates from AP_EXPENSE_REPORT_HEADERS. The view therefore behaves as a thin projection with a single computed column; it does not aggregate or join to lines or distributions, so each row corresponds to exactly one expense report header.

Key Columns

• REPORT_HEADER_ID — Primary key identifying the expense report header; the primary join key for lines, distributions, and workflow data.
• EMPLOYEE_ID, PAID_ON_BEHALF_EMPLOYEE_ID — The submitting employee and, where applicable, the employee on whose behalf the report is paid.
• INVOICE_NUM, VOUCHER_NUM, VOUCHNO — Invoice and voucher identifiers linking the report to its Payables invoice.
• TOTAL, MAXIMUM_AMOUNT_TO_APPLY, ADVANCE_INVOICE_TO_APPLY — Report total and the advance amount eligible/selected for application. ADVANCE_INVOICE_TO_APPLY is the column users most frequently search for, since it drives how outstanding advances offset the reimbursement.
• APPLY_ADVANCES_DEFAULT, PREPAY_APPLY_FLAG, PREPAY_NUM, PREPAY_APPLY_AMOUNT, PREPAY_GL_DATE — Advance/prepayment application controls and results.
• EXPENSE_STATUS_CODE — A computed column produced by AP_WEB_OA_ACTIVE_PKG.GETREPORTSTATUSCODE when the stored value is null, reflecting workflow-driven status.
• DEFAULT_CURRENCY_CODE, PAYMENT_CURRENCY_CODE, DEFAULT_EXCHANGE_RATE, MULTIPLE_CURRENCIES_FLAG — Currency and conversion attributes.
• ORG_ID — Multi-org operating unit identifier, essential for secure reporting.
• WORKFLOW_APPROVED_FLAG, CORE_WF_STATUS_FLAG, HOLD_LOOKUP_CODE, REJECT_CODE, EXPENSE_CURRENT_APPROVER_ID — Approval, hold, and rejection indicators.

Common Use Cases and Queries

Typical scenarios include identifying reports with unapplied advances, reconciling expense reports to invoices, and building approval or status dashboards scoped by operating unit.

• Reports where an advance is available to apply: SELECT report_header_id, invoice_num, total, advance_invoice_to_apply FROM apbv_expense_report_headers WHERE NVL(advance_invoice_to_apply,0) > 0 AND org_id = :p_org_id;
• Status and approval monitoring: SELECT report_header_id, employee_id, expense_status_code, workflow_approved_flag, expense_current_approver_id FROM apbv_expense_report_headers WHERE expense_status_code NOT IN ('APPROVED','PAID');
• Currency and payment review: SELECT report_header_id, default_currency_code, payment_currency_code, multiple_currencies_flag, total FROM apbv_expense_report_headers WHERE multiple_currencies_flag = 'Y';

Because the view includes the computed status column, queries benefit from real-time status evaluation, though this also means the package function executes per row; filtering by ORG_ID remains good practice.