Search Results ap_expense_feed_dists




Overview
Explore in AI Chat

Overview

APPS.AP_CARD_NOTIFICATIONS_V is a lightweight database view in the Oracle E-Business Suite Payables (AP) module. Its purpose is to expose a consolidated list of notification identifiers associated with corporate card expense feeds. In Oracle EBS 12.1.1 and 12.2.2, the view surfaces distinct notification IDs that drive workflow-related alerts and integration messages generated during corporate card expense processing. The view is owned by the APPS schema and is defined as a simple UNION of two SELECT DISTINCT statements against a single synonym, AP_EXPENSE_FEED_DISTS.

Because the view returns only identifiers — not descriptive attributes — it functions primarily as a lookup or reference companion to the underlying expense feed distribution data. Applications and concurrent programs that need to enumerate outstanding employee verification or manager approval notifications can query this view rather than filtering the base table directly, gaining a pre-deduplicated result set.

Underlying Base Objects

The view is defined over the referenced base object AP_EXPENSE_FEED_DISTS, exposed within the APPS schema as a synonym. The base table stores distribution lines and related identifiers for corporate card expense feeds imported into Payables. The view text is:

In each branch, the source column is aliased as NOTIFICATION_ID. The first branch reads EMPLOYEE_VERIFICATION_ID; the second reads MANAGER_APPROVAL_ID. Because the view uses UNION (not UNION ALL), any value appearing in both columns is returned only once. No joins, filters, or group-by clauses are applied, so the view reflects raw identifier values from the base table without additional business logic.

Key Columns

  • NOTIFICATION_ID — The single column exposed by the view. It is the alias applied to whichever source column is being selected. Populated from EMPLOYEE_VERIFICATION_ID in the first UNION branch and MANAGER_APPROVAL_ID in the second.

The view does not expose a discriminator column indicating whether a given NOTIFICATION_ID originated from the employee verification or the manager approval side of the union. Consumers that require that distinction must query AP_EXPENSE_FEED_DISTS directly and select the appropriate source column. Similarly, the view carries no employee, card, or expense attributes; those must be retrieved by joining back to the base table or related AP objects.

Common Use Cases and Queries

The view is typically used when an integration or reporting process needs a clean list of notification identifiers for corporate card expense activity. A common pattern is to enumerate all notification IDs for downstream workflow lookups:

  • SELECT NOTIFICATION_ID FROM APPS.AP_CARD_NOTIFICATIONS_V;

To check whether a specific notification exists before processing it:

  • SELECT NOTIFICATION_ID FROM APPS.AP_CARD_NOTIFICATIONS_V WHERE NOTIFICATION_ID = :p_notification_id;

To obtain the notification ID together with its originating context, query the base table instead:

  • SELECT EMPLOYEE_VERIFICATION_ID, MANAGER_APPROVAL_ID FROM APPS.AP_EXPENSE_FEED_DISTS;

Because the view performs DISTINCT and UNION operations with no indexes of its own, performance depends on indexing of the underlying columns in AP_EXPENSE_FEED_DISTS. For high-volume environments, filtering by specific identifiers against the base table is generally preferable to full scans of the view.