Search Results iby_upg_instruments




Overview
Explore in AI Chat

Overview

The IBY.IBY_UPG_INSTRUMENTS table is a Payments module data object within Oracle E-Business Suite, present and valid in both the 12.1.1 and 12.2.2 releases. It belongs to the IBY schema, the schema that underpins Oracle Payments and centralizes payment instrument, payment profile, and funds capture configuration for the E-Business Suite. The table stores instrument assignments: the association between a payment instrument and the party, organization, customer account, supplier site, or bank account use that is authorized to employ that instrument. In effect, it answers the question "which instrument may be used by which entity, and for which payment function."

The ETRM relationship metadata classifies this object as standalone under the heuristic Data Vault analysis. As a modeling suggestion, this indicates the table is neither a pure hub nor a classic dependent satellite from the perspective of its declared foreign keys; it holds its own surrogate key and references external master data without being strictly subordinate in the vault sense. Designers building an analytical or vault-style model should treat it as a self-sufficient assignment entity whose natural relationships are to customer and bank account master data rather than to internal IBY parents.

Key Information Stored

The physical schema documented for 12.2.2 contains 19 columns. The most significant are:

No unique business-key index is documented beyond the primary key, so INSTR_ASSIGNMENT_ID is the only confirmed unique identifier; business uniqueness is implied by the combination of instrument and assignment target rather than enforced by a documented alternate key.

Common Use Cases and Queries

Typical usage centers on validating which instruments a payer or payee may use, and on reconciling instrument configuration across upgrades. A representative query joining to the customer master is:

  • SELECT i.INSTR_ASSIGNMENT_ID, i.INSTRUMENT_TYPE, i.INSTRUMENT_ID, i.PAYMENT_FUNCTION, h.ACCOUNT_NUMBER FROM IBY.IBY_UPG_INSTRUMENTS i, HZ_CUST_ACCOUNTS h WHERE i.CUST_ACCOUNT_ID = h.CUST_ACCOUNT_ID;
  • SELECT i.INSTR_ASSIGNMENT_ID, i.INSTRUMENT_ID, b.BANK_ACCOUNT_NAME FROM IBY.IBY_UPG_INSTRUMENTS i, AP.AP_BANK_ACCOUNT_USES_ALL b WHERE i.BANK_ACCOUNT_USES_ID = b.BANK_ACCOUNT_USES_ID;

Reporting scenarios include auditing instrument assignments by organization (ORG_ID), identifying assignments lacking a supplier or customer target, and reconciliation during the 12.1.1 to 12.2.2 upgrade where instrument and bank account model changes must be verified.

Related Objects

The documented foreign keys and surrounding Payments schema yield the following significant relationships:

  • HZ_CUST_ACCOUNTS — joined via CUST_ACCOUNT_ID; the customer account master.
  • AP_BANK_ACCOUNT_USES_ALL — joined via BANK_ACCOUNT_USES_ID; defines bank account usage.
  • IBY_INSTRUMENTS — the instrument master referenced logically via INSTRUMENT_ID.
  • IBY_PAYMENT_PROFILES — payment profile configuration that consumes instrument assignments.
  • IBY_ACCT_SITE_USES and HZ_CUST_ACCT_SITES_ALL — support ACCT_SITE_USE_ID resolution.

Together these objects allow the assignment row to be resolved to a usable instrument, a payer or payee, and a funding bank account.