Results for “iby_payee_subkeys”

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

Overview

The IBY_PAYEE_SUBKEYS table is a core Payments (IBY) module object in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the encrypted equivalents of a payee's bank account details — commonly referred to as subkeys — and acts as the secure repository that ties a payer's stored payment instrument to a specific physical bank account and currency combination. The subkey exists because Oracle Payments separates the logical payee record from the sensitive instrument data that must be encrypted at rest and reconciled against a payment summary.

From a Data Vault modeling perspective, the metadata's heuristic classification places this table as satellite-leaning. This is a reasonable modeling suggestion: the table holds descriptive, largely non-identifying attributes that depend on a parent business key (the payee) and a surrogate account representation, rather than acting as an independent hub of business concepts. Analysts designing a warehouse layer should therefore treat IBY_PAYEE_SUBKEYS as a dependent satellite keyed to the payee hub.

Key Information Stored

The primary key is the single-column surrogate PAYEE_SUBKEY_ID, enforced through the constraint IBY_PAYEE_SUBKEYS_PK. No alternate business-key unique index is documented in the supplied metadata, so PAYEE_SUBKEY_ID should be treated as the sole unique identifier.

• PAYEE_SUBKEY_ID — surrogate primary key for each stored subkey record.
• MPAYEE_ID — foreign key to IBY_PAYEE, identifying the owning payee/payer record.
• SUBKEY_CIPHER_TEXT — the encrypted cipher text representing the bank account identifier; this is the security-critical payload of the table.
• USE_COUNT — a counter tracking how frequently the subkey has been referenced or reused, useful for purge and audit governance.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, enforcing multi-tenant/operating-unit data isolation.
• OBJECT_VERSION_NUMBER — optimistic-locking version stamp used by the OAF/ADF update path.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard Who columns providing audit lineage for inserts and updates.

Common Use Cases and Queries

Typical scenarios include reconciling a payment summary back to its encrypted subkey, auditing unused or stale subkeys, and validating that payees hold a registered instrument before a payment run. A representative join resolves a transaction summary to its owning payee:

• Summary-to-subkey reconciliation: join IBY_TRXN_SUMMARIES_ALL.SUB_KEY_ID to IBY_PAYEE_SUBKEYS.PAYEE_SUBKEY_ID to map payment summaries to encrypted bank records.
• Payee instrument audit: join MPAYEE_ID to IBY_PAYEE to list all subkeys held by a given payee.
• Security-scoped extraction: filter on SECURITY_GROUP_ID to restrict reporting to a single operating unit or tenant.
• Usage governance: aggregate USE_COUNT to identify dormant subkeys eligible for archival.

Because SUBKEY_CIPHER_TEXT is encrypted, queries generally return only the surrogate key and metadata; decrypted values are exposed solely through the Payments encryption APIs.

Related Objects

• IBY_PAYEE — parent table; join on IBY_PAYEE_SUBKEYS.MPAYEE_ID = IBY_PAYEE.MPAYEE_ID.
• IBY_TRXN_SUMMARIES_ALL — child table referencing this object via SUB_KEY_ID; establishes the summary-to-subkey link.
• FND_SECURITY_GROUPS — joined on SECURITY_GROUP_ID for multi-tenant partitioning.
• Payments encryption APIs — IBY public APIs that decrypt and validate subkey cipher text.