Search Results ap_cards




Overview
Explore in AI Chat

Overview

APPS.AP_CARDS_V is a reporting and integration view in Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 that presents corporate payment card data maintained by Oracle Payables. It denormalizes records from the AP_CARDS base table and joins them to card profile, card program, and person information so that consumers can query a single, human-readable result set without performing multi-table joins themselves. The view is commonly consumed by payment card administration screens, self-service cardholder pages, and outbound extracts used by card-issuing banks and expense management integrations. Because it resolves employee identity through PER_PEOPLE_X and applies HR security packages, it also respects the data access rules applied to person records within the EBS security model.

Underlying Base Objects

The view is defined over several documented objects:

The JOIN relationships are: AC.PROFILE_ID = ACP.PROFILE_ID(+), ACPR.CARD_PROGRAM_ID = AC.CARD_PROGRAM_ID, and AC.EMPLOYEE_ID = P.PERSON_ID(+).

Key Columns

Common Use Cases and Queries

Typical uses include cardholder rosters, active card listings, limit audits, and extracts for card issuers. A simple active-card query, which exploits the outer joins so that unassigned cards are not lost:

  • SELECT card_number, full_name, employee_number, card_program_name, profile_name, card_expiration_date FROM apps.ap_cards_v WHERE inactive_date IS NULL;
  • SELECT employee_number, full_name, card_number FROM apps.ap_cards_v WHERE card_program_id = :p_program_id ORDER BY full_name;

When querying this view, note that rows are filtered implicitly by HR security through PER_PEOPLE_X, so a report may return fewer rows when run under a restricted responsibility than when run by a user with unrestricted person access. Because the joins to AP_CARD_PROFILES and PER_PEOPLE_X are outer, CARD_NUMBER always reflects the card record even when profile or person data is missing.