Search Results cc_issuer_range_id

Overview

The IBY_CC_ISSUER_RANGES table is a core reference table within the Oracle E-Business Suite Payments (IBY) module. Its primary function is to store defined ranges of credit card numbers associated with specific card issuers, such as Visa, MasterCard, or American Express. This data is critical for the system's ability to identify the issuing institution of a card based solely on its number, a process known as Bank Identification Number (BIN) or Issuer Identification Number (IIN) validation. As noted in the official documentation, a key technical purpose of this table is to facilitate the removal of structural elements from a credit card number prior to its encryption, ensuring that sensitive data is stored in a standardized and secure format. It serves as a foundational lookup for payment processing, transaction validation, and reporting workflows in both EBS 12.1.1 and 12.2.2.

Key Information Stored

The table's structure is designed to map card number patterns to their respective issuers. While the full column list is not detailed in the provided excerpt, the primary and foreign keys reveal its critical elements. The CC_ISSUER_RANGE_ID column is the unique primary key identifier for each range record. The CARD_ISSUER_CODE is a foreign key linking to the IBY_CREDITCARD_ISSUERS_B table, which holds the master definition of the card issuer (e.g., name, brand). Typically, the table would also include columns defining the numeric range itself, such as RANGE_START and RANGE_END, or a PATTERN column (e.g., '4%' for Visa). These columns allow the system to determine if a given card number falls within a known issuer's allocated block.

Common Use Cases and Queries

The primary use case is the programmatic identification of a card's issuer during payment entry or transaction processing. A common SQL pattern involves querying the table to find the issuer code for a given card number by matching against the range. For reporting, the table is joined to transaction tables to summarize activity by card brand. Administrators may query it to verify or maintain the BIN range configuration.

• Issuer Identification: SELECT card_issuer_code FROM iby_cc_issuer_ranges WHERE :card_number BETWEEN range_start AND range_end;
• Validation Setup Report: SELECT icib.issuer_name, icir.range_start, icir.range_end FROM iby_cc_issuer_ranges icir, iby_creditcard_issuers_b icib WHERE icir.card_issuer_code = icib.issuer_code ORDER BY icib.issuer_name;

Related Objects

As indicated by the foreign key relationships, IBY_CC_ISSUER_RANGES is centrally connected to several key payment tables. IBY_CREDITCARD_ISSUERS_B is the parent table providing the issuer master data. IBY_CREDITCARD stores the encrypted card details and references a specific range record via CC_ISSUER_RANGE_ID. IBY_TRXN_SUMMARIES_ALL, which holds transaction summaries, also references this table to link transactions to the card issuer's range. These relationships ensure referential integrity and enable consistent issuer information across the payment lifecycle.