Search Results iby_creditcard




Overview
Explore in AI Chat

Overview

The IBY_CREDITCARD table is a core data repository within the Oracle E-Business Suite (EBS) Payments (IBY) module. It serves as the central table for storing detailed credit card information for both payers (customers) and payees. This table is fundamental to the payment processing infrastructure, enabling the secure storage and management of credit card instruments used in various financial transactions, such as customer payments, supplier disbursements, and employee expense reimbursements. Its status as VALID across both EBS 12.1.1 and 12.2.2 indicates its critical and stable role in the application architecture.

Key Information Stored

The table's primary key is the INSTRID (Instrument ID), which uniquely identifies each credit card record. Key columns, as indicated by its foreign key relationships, store essential card details and associated metadata. These include the CARD_ISSUER_CODE linking to the card brand (e.g., Visa, Mastercard), the ACCTTYPEID defining the account type, and the CARD_OWNER_ID referencing the HZ_PARTIES table to identify the cardholder. For security, the actual credit card number is not stored in plain text; instead, the table references the IBY_CREDITCARD.CC_NUM_SEC_SEGMENT_ID for tokenized or securely stored number segments. Additional columns store billing address details (ADDRESSID, BILL_ADDR_TERRITORY_CODE) and a link to issuer-specific validation ranges (CC_ISSUER_RANGE_ID).

Common Use Cases and Queries

This table is central to operations involving stored credit cards. Common use cases include generating reports on active customer payment methods, validating card details during transaction setup, and managing card lifecycle events (e.g., expiration updates). A typical query might join IBY_CREDITCARD with party and address tables to retrieve a cardholder's details for customer service or audit purposes. For example, a report to list all credit cards for a specific customer party would filter on CARD_OWNER_ID. Integration with the Payables module, via the AP_CARDS_ALL.CARD_REFERENCE_ID foreign key, is crucial for managing corporate purchasing cards (P-Cards). Developers often interact with this table indirectly through published Payment APIs rather than via direct DML to ensure data integrity and security compliance.

Related Objects

The IBY_CREDITCARD table has significant integration within the EBS data model. Key related objects, as per the provided metadata, include:

  • IBY_CREDITCARD_H: A history table that tracks changes to credit card records, linked via INSTRID.
  • IBY_INSTRHOLDER: Likely stores the assignment of payment instruments (including credit cards) to specific payment entities.
  • HZ_PARTIES & HZ_PARTY_SITE_USES: Oracle Trading Community Architecture tables providing the cardholder's identity and billing address information.
  • IBY_CREDITCARD_ISSUERS_B & IBY_CC_ISSUER_RANGES: Reference tables for card brand definitions and valid card number ranges.
  • AP_CARDS_ALL: The Oracle Payables table for purchasing card programs, which references IBY_CREDITCARD as its underlying instrument.
  • IBY_ACCTTYPE & FND_TERRITORIES: Lookup tables for account type and territory codes, respectively.
These relationships underscore the table's role as a master source for credit card data consumed by multiple EBS modules.