Results for “notification_id”

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

Overview

AP_CARD_NOTIFICATIONS_V is a read-only database view owned by the APPS schema in Oracle E-Business Suite, classified under the AP - Payables product family. Its documented purpose is to ensure that multiple notifications for the same open transactions are not received in WebExpenses. In practice, the view acts as a de-duplication and consolidation layer: it returns a single, distinct list of notification identifiers drawn from the expense feed distribution records, thereby preventing WebExpenses from surfacing redundant alerts for a transaction that is already pending action. The object holds a VALID status in both EBS 12.1.1 and 12.2.2, and no structural differences are documented between the two releases.

Underlying Base Objects

The view is defined over a single documented base object, AP_EXPENSE_FEED_DISTS, which is referenced through a SYNONYM in the APPS schema. This table stores the distribution-level detail of corporate card expense feeds as they flow from card providers into Payables for processing, matching, and reimbursement. Two distinct workflow identifiers exist on that table — EMPLOYEE_VERIFICATION_ID and MANAGER_APPROVAL_ID — each representing a point at which a notification may be raised. Rather than exposing both columns separately, the view text normalises them into one logical column through a UNION of two SELECT DISTINCT statements. The UNION operator implicitly removes duplicate rows across both branches, so an identifier appearing in either source, or coincidentally in both, is returned only once. This construction is the mechanism by which the "no duplicate notifications" guarantee is enforced.

Key Columns

• NOTIFICATION_ID — The only column exposed by the view. It is an alias, not a physical column: the first branch of the UNION selects EMPLOYEE_VERIFICATION_ID as NOTIFICATION_ID, and the second selects MANAGER_APPROVAL_ID as NOTIFICATION_ID, without an alias in the documented text. Values originate from the corresponding identifying columns on AP_EXPENSE_FEED_DISTS. Consumers should therefore treat NOTIFICATION_ID as an opaque workflow identifier rather than a foreign key to a single notification table, since a given value may correspond to an employee verification event or a manager approval event depending on its source branch. No other attributes — status, dates, amounts, or employee references — are projected, which keeps the view narrow and inexpensive to query.

Common Use Cases and Queries

The primary consumer is the WebExpenses integration, which queries the view to determine the current set of outstanding notifications before raising new ones. A typical pattern is an anti-join that suppresses alerts already in flight:

• Retrieving the full distinct notification set: SELECT notification_id FROM apps.ap_card_notifications_v;
• Suppressing duplicates during a notification run: SELECT :p_notification_id FROM dual WHERE :p_notification_id NOT IN (SELECT notification_id FROM apps.ap_card_notifications_v);
• Counting outstanding notification candidates for monitoring or reconciliation: SELECT COUNT(*) FROM apps.ap_card_notifications_v;

Because the view performs no joins beyond the UNION and exposes a single column, it is suitable for direct use in PL/SQL cursor loops and concurrent program logic. It should not be used to drive financial reporting, as it carries no amounts or accounting attributes. When referencing the object from custom code, always qualify it with the APPS schema or a synonym, and remember that the intent is strictly de-duplication of notification identifiers.