Results for “card_unmask_length”

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

Overview

The IBY_PAYMENTCARD table is a core data object within the IBY (Payments) product module of Oracle E-Business Suite. It stores payment card numbers and associated attributes for card programs configured under the card type "Payment Card." Records in this table are populated primarily through the Payables Credit Card setup flow in Oracle Payables, where card numbers are entered manually and subsequently associated with a card program, card owner, and billing address. The table therefore serves as the authoritative repository for purchaser and payment card reference data used during payment processing and reconciliation.

In terms of heuristic Data Vault classification, the foreign-key topology of IBY_PAYMENTCARD suggests a link (junction) model. The table resolves relationships between external entities such as HZ_PARTIES (card owner) and HZ_PARTY_SITE_USES (address), rather than acting as a standalone hub or a pure descriptive satellite. Modeling exercises should treat it as a link candidate, with the addressing and card-owner references functioning as the connected business keys.

Key Information Stored

The primary key is IBY_PAYMENTCARD_PK, defined on the INSTRID column. The same column is also referenced by the unique index IBY_PAYMENTCARD_INSTRID_U1, which serves as the documented business-key candidate. Among the 48 physical columns, the most operationally significant are:

• INSTRID – Surrogate primary key and business-key candidate uniquely identifying each card record.
• CARD_NUMBER / MASKED_CARD_NUMBER – The stored card number and its masked representation.
• EXPIRYDATE – Card expiration date used for validation during payment processing.
• CARD_OWNER_ID – Foreign key to HZ_PARTIES identifying the party that owns the card.
• ADDRESSID – Foreign key to HZ_PARTY_SITE_USES tying the card to a billing address.
• BILL_ADDR_TERRITORY_CODE – Foreign key to FND_TERRITORIES for the billing address territory.
• BILLING_ADDR_POSTAL_CODE – Postal code of the billing address, commonly required by card processors.
• CARD_ISSUER_CODE / CARD_NUMBER_LENGTH – Issuer and length metadata used for card validation.
• INSTRUMENT_TYPE / CARD_PURPOSE – Classification attributes describing the card's role.
• ACTIVE_FLAG / INACTIVE_DATE / SINGLE_USE_FLAG – Lifecycle and usage controls for the card.
• CARD_MASK_SETTING / CARD_UNMASK_LENGTH – Governance of how much of the card number is displayed.
• SECURITY_GROUP_ID – Foreign key to FND_SECURITY_GROUPS supporting multi-org / security access.
• OBJECT_VERSION_NUMBER – Optimistic locking column for concurrent updates.
• ATTRIBUTE1–15 – Descriptive flexfield segments for extensibility.
• REQUEST_ID / PROGRAM_ID / PROGRAM_APPLICATION_ID – Concurrent program traceability columns.

Common Use Cases and Queries

Practical uses of IBY_PAYMENTCARD include verifying card ownership prior to payment creation, reporting on active versus inactive cards, and auditing masked versus stored card numbers for PCI-related compliance. A typical query joins the card record to its owner and address:

• SELECT pc.instrid, pc.masked_card_number, pc.expirydate, p.party_name FROM iby_paymentcard pc, hz_parties p WHERE pc.card_owner_id = p.party_id AND pc.active_flag = 'Y';
• SELECT pc.instrid, pc.card_number, ps.address1 FROM iby_paymentcard pc, hz_party_site_uses ps WHERE pc.addressid = ps.party_site_use_id;
• SELECT pc.instrid, ft.territory_short_name FROM iby_paymentcard pc, fnd_territories ft WHERE pc.bill_addr_territory_code = ft.territory_code;

Reporting scenarios frequently filter on SINGLE_USE_FLAG or INACTIVE_DATE to determine card eligibility, while audit queries compare CARD_NUMBER against MASKED_CARD_NUMBER to detect masking configuration gaps.

Related Objects

The following objects have the most significant documented relationships with IBY_PAYMENTCARD:

• HZ_PARTIES – joined via IBY_PAYMENTCARD.CARD_OWNER_ID = HZ_PARTIES.PARTY_ID.
• HZ_PARTY_SITE_USES – joined via IBY_PAYMENTCARD.ADDRESSID = HZ_PARTY_SITE_USES.PARTY_SITE_USE_ID.
• FND_TERRITORIES – joined via IBY_PAYMENTCARD.BILL_ADDR_TERRITORY_CODE = FND_TERRITORIES.TERRITORY_CODE.
• FND_SECURITY_GROUPS – joined via IBY_PAYMENTCARD.SECURITY_GROUP_ID = FND_SECURITY_GROUPS.SECURITY_GROUP_ID.
• IBY_PAYMENTCARD_PK – the primary key constraint enforcing uniqueness on INSTRID.
• IBY_PAYMENTCARD_INSTRID_U1 – the unique index supplying the documented business-key candidate.