Results for “ap_card_programs_all”

50+ results




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

Overview

AP_CARD_PROGRAMS_ALL is the Payables (AP) schema table that stores the definition of every credit card program configured in an Oracle E-Business Suite instance. Each row represents one corporate card program — for example a company-branded Visa, MasterCard, or American Express program — and acts as the control record that governs how card transactions from that program are validated, matched to employees, expensed, reconciled, and cleared. The table is the master reference for the corporate card subsystem, and its surrogate primary key, CARD_PROGRAM_ID, is propagated to virtually every downstream card transaction and setup table.

Because card program definitions are organization-sensitive, the table carries ORG_ID and is therefore partitioned by operating unit through the multi-org security model. The _ALL suffix confirms that it uses the standard EBS multi-org naming convention rather than being a true global table. The documented physical schema in ETRM 12.2.2 lists 60 columns.

From a Data Vault modeling perspective, the foreign-key and referencing-table profile suggests a satellite-leaning classification: AP_CARD_PROGRAMS_ALL is heavily referenced by dependent tables (AP_CARDS_ALL, AP_CARD_PROFILES_ALL, AP_CARD_REQUESTS_ALL, AP_CC_ACCEPTORS, AP_EXPENSE_FEED_LINES_ALL, AP_CREDIT_CARD_TRXNS_ALL, AP_WEB_AMEX_PARAMS) and its own descriptors (program name, currency, vendor, clearing accounts, exclusion flags) behave more like attributes of a program entity than as an independent hub of transactional relationships.

Key Information Stored

The most operationally significant columns include:

Common Use Cases and Queries

Typical reporting and support queries list active card programs by operating unit, or trace which programs use a specific exception clearing account:

  • Listing programs: SELECT card_program_id, card_program_name, card_type_lookup_code, card_program_currency_code FROM ap_card_programs_all WHERE org_id = :org_id AND inactive_date IS NULL;
  • Finding programs by issuer vendor: join VENDOR_ID to PO_VENDORS to report which supplier each program settles through.
  • Auditing GL impact: join EXCEPTION_CLEARING_CCID to GL_CODE_COMBINATIONS to confirm the clearing account assignments.
  • Transaction volume analysis: aggregate AP_EXPENSE_FEED_LINES_ALL or AP_CREDIT_CARD_TRXNS_ALL by CARD_PROGRAM_ID to measure program activity.
  • Reconciliation exception reporting: use the EXCLUDE_*_FLAG columns to identify which programs suppress specific exception categories in the reconciliation workbench.

Related Objects

AP_CARD_PROGRAMS_ALL sits at the center of the corporate card data model. It is referenced by AP_CARDS_ALL (issued card definitions), AP_CARD_PROFILES_ALL (profile assignments), AP_CARD_REQUESTS_ALL (card requests), AP_CC_ACCEPTORS (acceptor records), AP_EXPENSE_FEED_LINES_ALL (downloaded expense feeds), AP_CREDIT_CARD_TRXNS_ALL (credit card transactions), and AP_WEB_AMEX_PARAMS (American Express feed parameters) — all via CARD_PROGRAM_ID. In the reverse direction, it depends on AP_CARD_CODE_SETS_ALL (CARD_CODE_SET_ID), FND_CURRENCIES (CARD_PROGRAM_CURRENCY_CODE), PO_VENDORS (VENDOR_ID), PO_VENDOR_SITES_ALL (VENDOR_SITE_ID), GL_CODE_COMBINATIONS (EXCEPTION_CLEARING_CCID), and AP_MAP_TYPES_B through both CARD_EXP_TYPE_MAP_TYPE_CODE and COUNTRY_MAP_TYPE_CODE. These relationships make the table the mandatory setup prerequisite before any card, code set, or feed can be defined.