Results for “ap_cards_all”

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

Overview

AP_CARDS_ALL is the Oracle Payables (AP) master table that stores information about payment cards issued to employees. In Oracle EBS 12.1.1 and 12.2.2, it functions as the central registry for corporate credit cards, procurement cards, and paycards managed through the Payables credit card module. Each row represents a single card assigned to an employee and links that card to its governing card program, card profile, and, where applicable, the associated employee record.

From a dimensional modeling perspective, the mined foreign key structure suggests a hub-leaning classification. The table holds the enduring business entity — the card itself — identified by a stable surrogate key, with descriptive and operational attributes layered on top. Practically, this makes AP_CARDS_ALL the anchor point for card-based expense and transaction processing, including credit card transaction feeds, employee card requests, and supplier-level card assignments.

Key Information Stored

AP_CARDS_ALL contains 59 documented columns. The most significant include:

• CARD_ID — The surrogate primary key (defined by index AP_CARDS_U1), uniquely identifying each card record.
• EMPLOYEE_ID — The employee to whom the card is issued; foreign key to PSB_EMPLOYEES.
• CARD_NUMBER — The card's masked or reference number used for identification.
• CARDMEMBER_NAME — The name printed on the card.
• CARD_PROGRAM_ID — Foreign key to AP_CARD_PROGRAMS_ALL, identifying the issuing bank program.
• PROFILE_ID — Foreign key to AP_CARD_PROFILES_ALL, defining card-level controls and limits.
• CARD_REFERENCE_ID / PAYCARD_REFERENCE_ID — References to IBY_CREDITCARD for secure card credential storage.
• CARD_EXPIRATION_DATE — Expiration date used for card lifecycle tracking.
• INACTIVE_DATE — Date the card was deactivated.
• ORG_ID — Multi-org operating unit identifier, enabling row-level security.
• REQUEST_ID — Foreign key to FND_CONCURRENT_REQUESTS, tracking the process that created or updated the card.
• DEPARTMENT_NAME, LOCATION_ID, COST_CENTER, GL_SUB_ACCOUNT — Organizational attribution for expense accounting.
• PHYSICAL_CARD_FLAG, PAPER_STATEMENT_REQ_FLAG, FLEET_SERVICE_FLAG — Operational flags governing card behavior.

Standard WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) and 30 ATTRIBUTE columns provide auditing and descriptive flexibility.

Common Use Cases and Queries

Typical scenarios include identifying all active cards for an employee, reconciling card transactions to card records, and reporting on cards by program or operating unit. A representative query joining cards to programs and employees:

• SELECT c.card_number, c.cardmember_name, p.program_name, c.card_expiration_date FROM ap_cards_all c, ap_card_programs_all p WHERE c.card_program_id = p.card_program_id AND c.org_id = :org_id AND c.inactive_date IS NULL;

Additional patterns include joining AP_CARDS_ALL to AP_CREDIT_CARD_TRXNS_ALL on CARD_ID to summarize spend per card, and joining to AP_EXPENSE_FEED_LINES_ALL for expense feed reporting. Security-conscious reports should reference CARD_REFERENCE_ID via IBY views rather than exposing raw card numbers.

Related Objects

• AP_CARD_PROFILES_ALL — joined on PROFILE_ID; defines card controls and limits.
• AP_CARD_PROGRAMS_ALL — joined on CARD_PROGRAM_ID; issuing bank program definition.
• AP_CREDIT_CARD_TRXNS_ALL — references CARD_ID; individual card transactions.
• AP_EXPENSE_FEED_LINES_ALL — references CARD_ID; imported expense feed lines.
• AP_CARD_DETAILS, AP_CARD_EMP_CANDIDATES, AP_CARD_REQUESTS_ALL, AP_CARD_SUPPLIERS_ALL — all reference CARD_ID for detail, eligibility, request, and supplier mappings.
• IBY_CREDITCARD — referenced via CARD_REFERENCE_ID for secure credential storage.
• FND_CONCURRENT_REQUESTS — referenced via REQUEST_ID for process auditing.
• PSB_EMPLOYEES — referenced via EMPLOYEE_ID for cardholder identification.