Results for “ap_card_expense_type_v”

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

Overview

AP_CARD_EXPENSE_TYPE_V is a public Oracle E-Business Suite view owned by the APPS schema in the Oracle Payables (AP) module. It exposes the set of valid corporate card expense type classifications used by Payables to categorize credit card transactions during expense reporting and card program processing. The view is a thin, purpose-built projection over Oracle Application Object Library (AOL) lookup data stored in AP_LOOKUP_CODES, returning the three columns LOOKUP_CODE, DISPLAYED_FIELD, and DESCRIPTION for one specific lookup type: 'CARD_EXPENSE_TYPE'.

Because it presents lookup values as a simple, denormalized row set, the view functions as a stable reference source for reports, list-of-values (LOV) definitions, interfaces, and analytics that must translate internal code values into user-facing labels. In Oracle EBS 12.1.1 and 12.2.2 the view remains valid and available to APPS, and any EBS responsibility with read access to AP lookup data can execute it directly. It is not a transactional object and contains no amounts, dates, or cardholder records; it is a controlled vocabulary for the expense-type dimension of credit card activity.

Underlying Base Objects

The documented view definition selects from AP_LOOKUP_CODES with a hard-coded predicate restricting LOOKUP_TYPE to 'CARD_EXPENSE_TYPE'. No joins, aggregations, or outer queries modify the result set, so the view is a filtered single-source projection whose grain matches one row per enabled card expense type lookup code.

The ETRM metadata for 12.2.2 records two referenced base objects:

• AP_LOOKUP_CODES (VIEW) — the immediate data source supplying LOOKUP_CODE, DISPLAYED_FIELD, and DESCRIPTION; it resolves to the underlying AP lookup tables maintained through the Payables lookup maintenance UI.
• FND_GLOBAL (PACKAGE) — the Oracle Applications session/context API, referenced because AP lookup views apply security and multi-org/session context (for example, ORG_ID or user context) when returning rows.

Because the source is a view over seeded and user-maintained lookup data, the population of AP_CARD_EXPENSE_TYPE_V reflects whatever enabled lookup values exist for CARD_EXPENSE_TYPE in the instance. Adding, disabling, or re-describing a card expense type in Payables lookup maintenance changes the rows returned by this view without any code deployment.

Key Columns

• LOOKUP_CODE — the internal code stored on card transactions and interface records. This column is the natural key: it is the value persisted in transaction-level columns that reference the expense type, and it is the value joined against in reporting queries.
• DISPLAYED_FIELD — the user-facing label presented in forms, LOVs, and reports. Selecting this column allows reports to render readable expense type names while retaining the code as the grouping key.
• DESCRIPTION — free-text explanation of the expense type. It is optional and often null for seeded values; it documents intended usage and can be surfaced in reference listings or reconciliation notes.

All three columns are character data. JOINs to other AP tables should be made on LOOKUP_CODE, not on DISPLAYED_FIELD, because displayed names are susceptible to localization and administrative edits.

Common Use Cases and Queries

Typical uses include validating card expense types during Payables interface loads, building LOVs for custom Oracle Forms or OAF pages, powering expense analysis dashboards, and producing reconciliation reports for corporate card programs. The following patterns are common:

• Reference listing of all valid card expense types:
  SELECT lookup_code, displayed_field, description FROM apps.ap_card_expense_type_v ORDER BY lookup_code;
• Resolving a stored code to a label for reporting:
  SELECT lookup_code, displayed_field FROM apps.ap_card_expense_type_v WHERE lookup_code = :p_expense_type;
• Joining card transaction data to obtain readable expense type names:
  SELECT t.card_number, t.amount, v.displayed_field FROM ap_card_transactions t, apps.ap_card_expense_type_v v WHERE t.expense_type = v.lookup_code;
• Validating externally supplied codes before an interface run:
  SELECT lookup_code FROM apps.ap_card_expense_type_v WHERE lookup_code IN ('AIR','LODG','MEAL');
• Detecting unlabeled or incomplete lookup maintenance:
  SELECT lookup_code FROM apps.ap_card_expense_type_v WHERE displayed_field IS NULL OR description IS NULL;

Because the view returns only enabled CARD_EXPENSE_TYPE lookups, it is the authoritative validation source for that dimension; any code absent from the view should be treated as invalid for Payables card processing.