Search Results ap_expense_report_headers_all




Overview
Explore in AI Chat

Overview

The AP_EXPENSE_REPORT_HEADERS_ALL table is a core transactional table within the Oracle E-Business Suite Payables (AP) module, specifically for releases 12.1.1 and 12.2.2. It serves as the primary repository for header-level information pertaining to employee expense reports. This table is fundamental to the expense report lifecycle, from creation and approval through to payment and accounting. Its multi-org structure, indicated by the "_ALL" suffix, allows it to store data for multiple operating units, with access controlled by the MOAC (Multi-Org Access Control) security profile. The table's integrity is maintained by the primary key AP_EXPENSE_REPORT_HEADERS_PK on REPORT_HEADER_ID and is centrally connected to numerous other Payables, General Ledger, and Purchasing entities via a network of foreign key relationships.

Key Information Stored

The table's columns capture the essential administrative and financial attributes of an expense report. The primary identifier is REPORT_HEADER_ID. Critical foreign key columns link the report to its core entities: EXPENSE_REPORT_ID connects to the source report in AP_EXPENSE_REPORTS_ALL, while VENDOR_ID and VENDOR_SITE_ID link to the employee's record as a supplier. Financial control is managed through SET_OF_BOOKS_ID, DEFAULT_CURRENCY_CODE, and DEFAULT_EXCHANGE_RATE_TYPE. The payment and accounting workflow is tracked via columns such as VOUCHNO (linking to the final Payables invoice), ACCTS_PAY_CODE_COMBINATION_ID (the liability account), EMPLOYEE_CCID (the employee's expense clearing account), and HOLD_LOOKUP_CODE. Additional audit and process columns like LAST_AUDITED_BY, REQUEST_ID, and ADVANCE_INVOICE_TO_APPLY (for offsetting cash advances) provide comprehensive tracking.

Common Use Cases and Queries

This table is central to reporting, data fixes, and process audits within Payables. Common analytical queries involve joining to related tables to create a holistic view of expense report activity. A frequent reporting use case is tracking the status and value of reports by operating unit and employee. For example:

  • Identifying expense reports pending approval or on hold.
  • Reconciling reported amounts to the final voucher and payment details by joining to AP_INVOICES_ALL.
  • Auditing the accounting distributions generated for expense reports by linking to AP_EXP_REPORT_DISTS_ALL.

A sample query pattern to list reports with their associated voucher number and total amount would join AP_EXPENSE_REPORT_HEADERS_ALL (ERH) to AP_INVOICES_ALL (INV) on ERH.VOUCHNO = INV.INVOICE_ID, filtering by SET_OF_BOOKS_ID and a creation date range.

Related Objects

As documented in the ETRM metadata, AP_EXPENSE_REPORT_HEADERS_ALL has extensive relationships with key EBS tables. It is the parent table for line and distribution details via foreign keys from AP_EXPENSE_REPORT_LINES_ALL.REPORT_HEADER_ID and AP_EXP_REPORT_DISTS_ALL.REPORT_HEADER_ID. It references the source expense report via AP_EXPENSE_REPORTS_ALL.EXPENSE_REPORT_ID. For payment processing, it links to AP_INVOICES_ALL twice: once for the final voucher (VOUCHNO) and once for any applied cash advance (ADVANCE_INVOICE_TO_APPLY). Accounting setup relationships exist with GL_SETS_OF_BOOKS_11I (SET_OF_BOOKS_ID), GL_CODE_COMBINATIONS (for CCIDs), and FND_CURRENCIES. It also links to supplier (PO_VENDORS, PO_VENDOR_SITES_ALL), audit (AP_AUD_AUDIT_REASONS), and system (FND_USER, FND_CONCURRENT_REQUESTS) tables, forming a comprehensive network within the application's data model.