Results for “card_issuer_name”

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

Overview

The IBY_CREDITCARD_ISSUERS_V view is a seeded, VALID database object owned by the APPS schema in Oracle E-Business Suite releases 12.1.1 and 12.2.2. It belongs to the IBY – Payments product family and provides a denormalized, language-aware presentation of credit card issuer configuration data held by the Payments foundation layer. Credit card issuers represent the financial institutions whose card brands and authorization rules are referenced during payment processing, refunds, and settlement.

Functionally, the view exists to shield callers from the underlying base/translation table split. Because descriptive attributes such as CARD_ISSUER_NAME and DESCRIPTION are stored in a translation table while control attributes reside in the base table, consumers would otherwise be required to write their own join and language filter. The view performs both, returning the correct translated issuer name for the session language. This makes it a natural reporting and integration surface for Oracle Payments, Oracle Payables, Oracle Receivables, and any custom component that must resolve a card issuer code to a human-readable issuer name.

Underlying Base Objects

Per the documented view text, IBY_CREDITCARD_ISSUERS_V is defined over two referenced base objects, both exposed to APPS as synonyms:

• IBY_CREDITCARD_ISSUERS_B — the base table holding issuer-level control attributes and standard WHO/audit columns. Aliased as B.
• IBY_CREDITCARD_ISSUERS_TL — the translation table holding language-specific descriptive text. Aliased as T.

The two objects are joined on CARD_ISSUER_CODE, with the translation side additionally filtered by T.LANGUAGE = USERENV('LANG'). That predicate restricts rows to the language of the current database session, so the view always yields exactly one descriptive row per issuer code. The literal B.ROWID is projected as ROW_ID, giving consumers a stable pseudo-key for the base row. Because the view is defined over the _B/_TL pair, it is a read-only construct; DML must be directed at the underlying tables through the Payments APIs.

Key Columns

• ROW_ID — the ROWID of the underlying IBY_CREDITCARD_ISSUERS_B row, useful as a unique identifier in extracts.
• CARD_ISSUER_CODE — the primary business key and the join column between base and translation tables; the code used on payment instrument records.
• CARD_ISSUER_NAME — the translated issuer name; this is the column most frequently searched for and the one that answers the common query "card_issuer_name."
• DESCRIPTION — the translated long description of the issuer.
• CARD_ISSUER_ACCEPTED_FLAG — indicates whether the issuer is accepted for use.
• AUTHORIZATION_VALIDITY_PERIOD — the interval for which an authorization remains valid.
• DIGIT_CHECK_FLAG — controls whether card-number digit (Luhn) validation applies.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, OBJECT_VERSION_NUMBER — standard audit and optimistic locking columns carried from the base table.

Common Use Cases and Queries

Typical scenarios include validating issuer setup before enabling a card brand, populating list-of-values prompts, and producing lookup extracts that map issuer codes to names for reconciliation and payment reporting. The following query lists all active issuers in the session language:

SELECT card_issuer_code,
       card_issuer_name,
       description,
       card_issuer_accepted_flag,
       authorization_validity_period,
       digit_check_flag
FROM   apps.iby_creditcard_issuers_v
WHERE  card_issuer_accepted_flag = 'Y'
ORDER  BY card_issuer_name;

To resolve a single issuer by name — the "card_issuer_name" lookup pattern — use:

SELECT card_issuer_code,
       card_issuer_name
FROM   apps.iby_creditcard_issuers_v
WHERE  card_issuer_name = :p_issuer_name;

For audit reporting across setup changes, the WHO columns support standard date-range filtering:

SELECT card_issuer_code,
       card_issuer_name,
       last_updated_by,
       last_update_date
FROM   apps.iby_creditcard_issuers_v
WHERE  last_update_date >= :p_from_date;

In all cases the commitment is read-only, and results reflect the language of the querying session rather than a fixed locale.