Results for “card_owner_id”

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

Overview

IBY_CREDITCARD_V is an APPS-owned database view in the Oracle E-Business Suite Payments (IBY) module that exposes registered credit card information stored in the payment instrument repository. It is classified in ETRM as a VIEW with VALID status, and its stated purpose is to provide a working interface to registered credit cards. In EBS 12.1.1 and 12.2.2, the IBY schema holds payment instrument data used by iPayment, Oracle Payments, and related funds capture and disbursement flows. This view acts as a queryable projection over the underlying credit card table, presenting both legacy and hash-based card number representations together with cardholder, instrument, and encryption attributes.

The view is particularly relevant to users searching for the column "cc_number_hash1." Rather than reading the base table directly, the view surfaces CCNUMBER, CC_NUMBER_HASH1, and CC_NUMBER_HASH2 side by side, which is useful where card numbers are tokenized or hashed for security and matching requirements.

Underlying Base Objects

Per the documented metadata, IBY_CREDITCARD_V is defined over IBY_CREDITCARD, referenced through a synonym. The view text is a straightforward projection:

SELECT C.INSTRID, C.CARD_OWNER_ID, C.CCNUMBER, C.CC_NUMBER_HASH1,
       C.CC_NUMBER_HASH2, C.EXPIRYDATE, C.FINAME, NULL, C.CHNAME,
       C.INSTRNAME, NULL, NULL, C.DESCRIPTION INSTRBUF, C.ENCRYPTED
FROM IBY_CREDITCARD C

No joins, filters, or aggregations are applied. The view simply renames DESCRIPTION to INSTRBUF and injects three NULL placeholders corresponding to ACCTTYPE, OWNERTYPE, and OWNERID. Because it is a single-table projection, the view inherits the security posture and access grants of the base instrument table; any row-level or card-number masking applied at the base object level continues to apply.

Key Columns

• INSTRID — Primary instrument identifier for the registered card.
• CARD_OWNER_ID — Identifier of the party or account that owns the card.
• CCNUMBER — The stored card number (subject to encryption/masking rules).
• CC_NUMBER_HASH1 / CC_NUMBER_HASH2 — Hash values derived from the card number, used for matching and duplicate detection without exposing the clear number.
• EXPIRYDATE — Card expiry date.
• FINAME — First name associated with the instrument.
• CHNAME — Cardholder name.
• INSTRNAME — Instrument name or label.
• INSTRBUF — Aliased from DESCRIPTION; descriptive buffer text for the instrument.
• ENCRYPTED — Flag indicating whether the stored card number is encrypted.
• ACCTTYPE, OWNERTYPE, OWNERID — Exposed as NULL in the view text and are not populated through this view.

Common Use Cases and Queries

Typical uses include reconciling registered cards against hash values, auditing encryption status, and validating cardholder data for payments troubleshooting. Example queries:

SELECT instrid, card_owner_id, cc_number_hash1, expiry_date
FROM   apps.iby_creditcard_v
WHERE  cc_number_hash1 = :p_hash;

SELECT instrid, instname, chname, encrypted
FROM   apps.iby_creditcard_v
WHERE  encrypted = 'Y';

SELECT card_owner_id,
       COUNT(*) card_count
FROM   apps.iby_creditcard_v
GROUP  BY card_owner_id;

When joining to owner or instrument-type lookups, note that OWNERTYPE and OWNERID return NULL from this view; source those attributes from the base IBY_CREDITCARD table or related IBY objects instead. Always respect Payments security and masking conventions when querying card data.