Results for “cc_issuer_range_id”

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

Overview

The IBY.IBY_CC_ISSUER_RANGES table is a Payments (IBY) module reference object that stores credit card issuer ranges — the numeric prefix and length patterns that identify the card brand or issuer for a given card number. Its documented purpose is to remove structure from a credit card number before that number is encrypted, ensuring that sensitive PAN data is masked consistently while still permitting downstream processes to identify the issuer. In Oracle EBS 12.1.1 and 12.2.2, this table is part of the Payments foundation schema and is referenced by several transactional and security-related tables that store the resulting issuer range identifier rather than recomputing it.

Based on the heuristic Data Vault classification mined from the foreign key structure, this object is best modeled as hub-leaning: it holds a stable set of business keys (issuer ranges) that are referenced by multiple dependent tables. In practice this means the table behaves as a reference/dimension master, while the tables that point to it act as satellites or links carrying transactional context.

Key Information Stored

The table is owned by the IBY schema and contains eleven documented columns in the 12.2.2 physical schema. The most significant are:

• CC_ISSUER_RANGE_ID — surrogate primary key, enforced by IBY_CC_ISSUER_RANGES_PK. This is the identifier propagated to dependent tables.
• CARD_ISSUER_CODE — foreign key to IBY_CREDITCARD_ISSUERS_B, linking each range to its parent issuer definition.
• CARD_NUMBER_PREFIX — the leading digit sequence used to recognize a card as belonging to the issuer.
• CARD_NUMBER_LENGTH — the expected length of the card number for the matching issuer range.
• OBJECT_VERSION_NUMBER — optimistic locking / concurrency control column typical of the IBY schema.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns tracking insert and update attribution.
• ZD_EDITION_NAME — editioning column supporting Online Patching (Edition-Based Redefinition) in 12.2.x.

The business-key candidate is defined through the unique index IBY_CC_ISSUER_RANGES_U1, which spans CC_ISSUER_RANGE_ID and ZD_EDITION_NAME. This composite uniqueness reflects EBR editioning rather than an independent natural key; the meaningful business identification remains the combination of CARD_ISSUER_CODE, CARD_NUMBER_PREFIX, and CARD_NUMBER_LENGTH.

Common Use Cases and Queries

Typical usage centers on card-brand identification, encryption preprocessing, and audit/reporting of payment transactions by issuer.

• Resolving an issuer for a card prefix:

  SELECT r.cc_issuer_range_id, r.card_issuer_code,
         r.card_number_prefix, r.card_number_length
  FROM   iby.iby_cc_issuer_ranges r
  WHERE  :prefix LIKE r.card_number_prefix || '%'
  AND    LENGTH(:card_number) = r.card_number_length;

• Joining to issuer master data for reporting:

  SELECT i.issuer_name, r.card_number_prefix, r.card_number_length
  FROM   iby.iby_cc_issuer_ranges r,
         iby.iby_creditcard_issuers_b i
  WHERE  r.card_issuer_code = i.card_issuer_code;

• Aggregating transactions by issuer range using IBY_TRXN_SUMMARIES_ALL.
• Validating that every IBY_CREDITCARD row maps to a valid, current issuer range.

Related Objects

The following objects are documented as participating in the FK/PK relationships with IBY_CC_ISSUER_RANGES:

• IBY_CREDITCARD_ISSUERS_B — referenced via CARD_ISSUER_CODE; supplies issuer definitions.
• IBY_CREDITCARD — references this table via CC_ISSUER_RANGE_ID; stores payment card records.
• IBY_TRXN_SUMMARIES_ALL — references via CC_ISSUER_RANGE_ID; summarized payment transactions.
• OE_TRXN_TEMP — references via CC_ISSUER_RANGE_ID; order-entry temporary transaction rows.
• IBY_SECURITY_SEGMENTS — references via CC_ISSUER_RANGE_ID; security segmentation used for masking.

Together these relationships confirm the table's role as a hub-style reference consumed by credit card, transaction summary, order entry, and security segmentation components across the Oracle Payments and Order Management flows.