Search Results ap_cards_all

Overview

The AP_CARDS_ALL table is a core data repository within the Oracle E-Business Suite Payables (AP) module, specifically for the management of corporate credit card programs. It serves as the master table for storing detailed information about individual credit cards issued to employees. Its primary role is to maintain the cardholder relationship, link a physical or virtual card to an employee and a specific card program, and act as a central reference point for all subsequent credit card transaction processing, reconciliation, and reporting. As an "ALL" table, it is a multi-organization structure, meaning it contains data for all operating units, with access typically controlled by the MOAC (Multi-Org Access Control) security model.

Key Information Stored

The table's structure is designed to capture essential card attributes and relationships. Its primary key is the CARD_ID, a unique system-generated identifier. Critical foreign key columns establish vital links: CARD_PROGRAM_ID associates the card with a defined program in AP_CARD_PROGRAMS_ALL, while PROFILE_ID links to configuration rules in AP_CARD_PROFILES_ALL. The table stores the cardholder's identity via the EMPLOYEE_ID (linking to PER_ALL_PEOPLE_F) and connects to the payment system by referencing a card template in IBY_CREDITCARD through CARD_REFERENCE_ID. Other significant columns track the card's status (e.g., active, lost, cancelled), issue and expiration dates, credit limits, and the last reconciliation details. The REQUEST_ID column can link to FND_CONCURRENT_REQUESTS for processes like card generation.

Common Use Cases and Queries

This table is central to queries supporting card administration, audit, and reconciliation. Common scenarios include generating a list of all active cards for an operating unit, identifying cards nearing expiration, and analyzing card usage by employee or program. A typical query might join to employee and program tables to create a management report:

• SELECT ac.card_number, ppf.full_name, acp.program_name, ac.creation_date, ac.expiration_date FROM ap_cards_all ac, per_all_people_f ppf, ap_card_programs_all acp WHERE ac.employee_id = ppf.person_id AND ac.card_program_id = acp.card_program_id AND ac.org_id = :p_org_id AND sysdate BETWEEN ppf.effective_start_date AND ppf.effective_end_date;

For reconciliation, the table is joined to AP_CREDIT_CARD_TRXNS_ALL to match transactions to their source card. Support teams also query it to troubleshoot issues with card feeds or expense report imports that reference a specific CARD_ID.

Related Objects

As indicated by its foreign key relationships, AP_CARDS_ALL is a pivotal hub in the credit card sub-schema. Key documented relationships include:

• Parent References: It references AP_CARD_PROFILES_ALL (PROFILE_ID), AP_CARD_PROGRAMS_ALL (CARD_PROGRAM_ID), FND_CONCURRENT_REQUESTS (REQUEST_ID), and IBY_CREDITCARD (CARD_REFERENCE_ID).
• Child Dependencies: Several transactional and setup tables use CARD_ID as a foreign key, including:
  • AP_CARD_DETAILS: Stores individual card-level limits and settings.
  • AP_CREDIT_CARD_TRXNS_ALL: The primary table for imported credit card transactions.
  • AP_EXPENSE_FEED_LINES_ALL: Holds expense line items sourced from card feeds.
  • AP_CARD_REQUESTS_ALL, AP_CARD_EMP_CANDIDATES, and AP_CARD_SUPPLIERS_ALL for card request and candidate management.