Results for “ap_card_suppliers”

46 results




Overview
Explore in AI Chat

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

Overview

AP_CARD_SUPPLIERS_V is a view owned by the APPS schema within the Oracle Payables (AP) module. As documented in the ETRM repository for EBS 12.1.1 and 12.2.2, the view holds all information relating to the Supplier, Supplier Site, and Credit Card combination, with exactly one row returned per combination. In practice, it acts as a thin, reporting-friendly projection over the underlying AP_CARD_SUPPLIERS table, exposing the association between a corporate credit card and the supplier and supplier site against which that card may be used.

This association is central to the Procure-to-Pay credit card flows in Payables, where card programs, card issuance, and supplier acceptance must be traceable. Because the view is a simple, single-object projection, it performs well in reporting and integration scenarios and is commonly surfaced through Oracle BI Publisher reports, custom concurrent programs, and inbound/outbound interfaces that need to resolve a card to its supplier context.

Underlying Base Objects

The only documented referenced base object is AP_CARD_SUPPLIERS, exposed through a synonym of the same name. The view definition is a straightforward SELECT over that object:

There are no joins, filters, or aggregation in the view text, so it does not alter or restrict the rows in the base object. The view therefore inherits the granularity of AP_CARD_SUPPLIERS — one record per card, supplier, and site combination — and its behavior and data volume mirror the base table exactly. The inclusion of ROWID reflects the standard Oracle EBS pattern for views used by the Forms-based framework and for row-level identification.

Key Columns

The columns exposed by the view are documented as follows:

  • CARD_ID — The unique identifier of the credit card record. This is the primary key of the card definition and the column most frequently used in joins to other Payables card objects.
  • VENDOR_ID — The supplier (vendor) identifier associated with the card. Joins to AP_SUPPLIERS (via vendor_id) resolve supplier names and details.
  • VENDOR_SITE_ID — The supplier site identifier. Joins to AP_SUPPLIER_SITES_ALL resolve site names and addresses.
  • ORG_ID — The operating unit identifier, supporting multi-org (MOAC) security and filtering.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard audit columns recording when, by whom, and through which login the row was last modified.
  • CREATION_DATE, CREATED_BY — Standard audit columns recording initial creation.
  • ROWID — The physical row identifier exposed by the view; documented in the column list as ROW_ID.

Common Use Cases and Queries

A frequent requirement is to find all suppliers and sites enabled for a given card, or all cards enabled for a given supplier. The sample query below resolves a card and joins to supplier and site tables for descriptive reporting:

  • SELECT v.card_id, v.vendor_id, s.vendor_name, v.vendor_site_id, v.org_id FROM ap_card_suppliers_v v, ap_suppliers s WHERE v.vendor_id = s.vendor_id AND v.card_id = :p_card_id;

Because the user's search term was "card_id", the most common navigation is by that column, either to confirm which vendors a card is valid against or to obtain the row for maintenance and reconciliation. Typical scenarios include:

  • Validating card-to-supplier setup before processing credit card transactions in Payables.
  • Reporting on card program coverage by supplier and operating unit, filtered by org_id under MOAC.
  • Extracting audit information (created_by, last_updated_by, timestamps) for change tracking and SOX compliance reporting.

Given the view performs no filtering, any row-level restriction — by operating unit, card status, or supplier — must be applied in the calling query. Users should join to AP_CARDS_ALL for card descriptive attributes and to supplier tables for names and sites, as the view itself exposes identifiers only.