Results for “ap_expense_report_status_v”

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

Overview

AP_EXPENSE_REPORT_STATUS_V is a dictionary view owned by the APPS schema in Oracle E-Business Suite Payables (AP). Its specific and sole purpose is to expose the valid codes, displayed values, and descriptions of the "Expense Report Status" lookup type maintained in Oracle Payables. Rather than presenting transactional expense report data, the view acts as a controlled reference list that defines the lifecycle states an expense report can hold — for example statuses such as Pending, Approved, Rejected, Paid, or Withdrawn — depending on how the lookup has been configured in a given implementation.

The object holds the status VALID in ETRM and is documented for both 12.1.1 and 12.2.2. Because it resolves to a lookup rather than a transactional entity, it is generally used in reporting and integration scenarios that need to translate a stored numeric or coded status into a human-readable label, or to validate the set of legitimate statuses in force at a customer site. Lookup values are customer-configurable, so the view reflects the live configuration of the environment in which it is queried.

Underlying Base Objects

The documented definition is concise. AP_EXPENSE_REPORT_STATUS_V is defined over AP_LOOKUP_CODES, itself a view rather than a base table, and the ETRM metadata lists FND_GLOBAL (PACKAGE) as an additional referenced object. The AP_LOOKUP_CODES view supplies the lookup repository rows; FND_GLOBAL is referenced in the broader lookup framework to resolve the current application and session context (for example the logged-in user and application identifier) used when lookups are defined and secured.

The documented view text is:

• SELECT LOOKUP_CODE, DISPLAYED_FIELD, DESCRIPTION FROM AP_LOOKUP_CODES WHERE LOOKUP_TYPE = 'EXPENSE REPORT STATUS'

This confirms the view is a simple filtered projection: no joins, aggregations, or calculations beyond the single predicate on LOOKUP_TYPE.

Key Columns

• LOOKUP_CODE — the stored internal code for the expense report status. This is the value persisted on the underlying transactional records (for example expense report headers) and is the column most commonly joined against.
• DISPLAYED_FIELD — the user-facing text rendered in the Payables user interface for the given lookup code. This is the label suitable for presentation in reports, dashboards, or extracts.
• DESCRIPTION — a free-text description of the status, providing additional business context beyond the display name.

Common Use Cases and Queries

Typical uses include populating status prompt lists, resolving coded statuses to display text within custom reports, and validating that an expected status exists before integration logic acts on it. The following query returns all currently configured expense report statuses in the environment:

• SELECT lookup_code, displayed_field, description FROM apps.ap_expense_report_status_v ORDER BY lookup_code;

The view is also commonly joined to an expense report header, matching the stored status code against LOOKUP_CODE, so that the display text can be derived alongside the report data.

Because the underlying source is a customer-maintained lookup, results vary by implementation; readers should query the view directly in their target environment rather than assuming a fixed set of statuses.