Search Results iby_instrholder




Overview

The IBY_INSTRHOLDER table is a core data object within the Oracle Payments (IBY) module of Oracle E-Business Suite (EBS) versions 12.1.1 and 12.2.2. It serves as a junction table that defines the relationship between a payment instrument and the entity that holds or owns it. As per the official documentation, its primary role is to store information about the holder of an instrument, enabling a single payment instrument—such as a bank account or credit card—to be associated with different users, payees, or payers within the system. This design is fundamental for supporting flexible payment processing and instrument management across various business entities.

Key Information Stored

The table's structure is defined by a composite primary key that uniquely identifies each instrument-holder relationship. The critical columns are:

  • INSTRID: The unique identifier for the payment instrument (e.g., a specific bank account or credit card).
  • INSTRTYPE: The type of the payment instrument, which determines the related detail table (e.g., 'BANKACCT' or 'CREDITCARD').
  • OWNERID: The unique identifier for the entity that holds the instrument.
  • OWNERTYPE: The type of the holder entity (e.g., user, payee, payer).

This schema allows the system to answer the question: "Which specific entity (OWNERTYPE/OWNERID) holds which specific payment instrument (INSTRTYPE/INSTRID)?"

Common Use Cases and Queries

A primary use case is retrieving all payment instruments held by a particular entity, such as a supplier payee, for payment processing or reporting. Conversely, administrators may need to identify all holders of a specific instrument for audit or security purposes. Common SQL queries involve joining IBY_INSTRHOLDER to instrument detail tables like IBY_BANKACCT or IBY_CREDITCARD using INSTRID and INSTRTYPE. For example, to find all bank accounts held by a payee with ID 1000:

  • SELECT ba.* FROM iby_instrholder ih, iby_bankacct ba WHERE ih.instrid = ba.bankacctid AND ih.instrtype = 'BANKACCT' AND ih.ownerid = 1000 AND ih.ownertype = 'PAYEE';

This table is also central for payment setup validation, ensuring that payment instructions are only processed for valid instrument-holder relationships.

Related Objects

IBY_INSTRHOLDER has direct foreign key relationships with the primary payment instrument tables, as documented. Its INSTRID column references IBY_CREDITCARD and IBY_BANKACCT, depending on the INSTRTYPE value. It is a foundational table for higher-level payment processing logic and is referenced by various Payment APIs and user interfaces that manage instrument assignment. While not listed in the brief metadata, related views such as IBY_PAYER_ALL_INSTRUMENTS_V or IBY_EXT_BANK_ACCOUNTS_V likely join to this table to present consolidated instrument information. Understanding its relationship with the OWNERTYPE and OWNERID columns also requires knowledge of the specific entity tables (e.g., AP_SUPPLIERS for payees) those values reference.

  • Table: IBY_INSTRHOLDER 12.2.2

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_INSTRHOLDER,  object_name:IBY_INSTRHOLDER,  status:VALID,  product: IBY - Paymentsdescription: IBY_INSTRHOLDER stores the information about the holder of the instrment. A payment instrument can be held by different users or payees or payers. ,  implementation_dba_data: IBY.IBY_INSTRHOLDER

  • Table: IBY_INSTRHOLDER 12.1.1

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_INSTRHOLDER,  object_name:IBY_INSTRHOLDER,  status:VALID,  product: IBY - Paymentsdescription: IBY_INSTRHOLDER stores the information about the holder of the instrment. A payment instrument can be held by different users or payees or payers. ,  implementation_dba_data: IBY.IBY_INSTRHOLDER

  • View: IBY_INSTR_HOLDER_V 12.2.2

    owner:APPS,  object_type:VIEW,  fnd_design_data:IBY.IBY_INSTR_HOLDER_V,  object_name:IBY_INSTR_HOLDER_V,  status:VALID,  product: IBY - Paymentsimplementation_dba_data: APPS.IBY_INSTR_HOLDER_V

  • View: IBY_INSTR_HOLDER_V 12.1.1

    owner:APPS,  object_type:VIEW,  fnd_design_data:IBY.IBY_INSTR_HOLDER_V,  object_name:IBY_INSTR_HOLDER_V,  status:VALID,  product: IBY - Paymentsimplementation_dba_data: APPS.IBY_INSTR_HOLDER_V

  • Table: IBY_BANKACCT 12.2.2

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_BANKACCT,  object_name:IBY_BANKACCT,  status:VALID,  product: IBY - Paymentsdescription: IBY_BANKACCOUNTstores bank account related information of the customer(payer) or payee. ,  implementation_dba_data: IBY.IBY_BANKACCT

  • Table: IBY_BANKACCT 12.1.1

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_BANKACCT,  object_name:IBY_BANKACCT,  status:VALID,  product: IBY - Paymentsdescription: IBY_BANKACCOUNTstores bank account related information of the customer(payer) or payee. ,  implementation_dba_data: IBY.IBY_BANKACCT

  • Table: IBY_CREDITCARD 12.1.1

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_CREDITCARD,  object_name:IBY_CREDITCARD,  status:VALID,  product: IBY - Paymentsdescription: IBY_CREDITACRD stores Credit Card related information of the customer(payer) or payee. ,  implementation_dba_data: IBY.IBY_CREDITCARD

  • View: IBY_PURCHASECARD_V 12.2.2

    owner:APPS,  object_type:VIEW,  fnd_design_data:IBY.IBY_PURCHASECARD_V,  object_name:IBY_PURCHASECARD_V,  status:VALID,  product: IBY - Paymentsdescription: View used to work with registered purchase cards. ,  implementation_dba_data: APPS.IBY_PURCHASECARD_V

  • View: IBY_BANKACCT_V 12.2.2

    owner:APPS,  object_type:VIEW,  fnd_design_data:IBY.IBY_BANKACCT_V,  object_name:IBY_BANKACCT_V,  status:VALID,  product: IBY - Paymentsdescription: View used to work with registered bank accounts. ,  implementation_dba_data: APPS.IBY_BANKACCT_V

  • View: IBY_PURCHASECARD_V 12.1.1

    owner:APPS,  object_type:VIEW,  fnd_design_data:IBY.IBY_PURCHASECARD_V,  object_name:IBY_PURCHASECARD_V,  status:VALID,  product: IBY - Paymentsdescription: View used to work with registered purchase cards. ,  implementation_dba_data: APPS.IBY_PURCHASECARD_V

  • View: IBY_BANKACCT_V 12.1.1

    owner:APPS,  object_type:VIEW,  fnd_design_data:IBY.IBY_BANKACCT_V,  object_name:IBY_BANKACCT_V,  status:VALID,  product: IBY - Paymentsdescription: View used to work with registered bank accounts. ,  implementation_dba_data: APPS.IBY_BANKACCT_V

  • Table: IBY_CREDITCARD 12.2.2

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_CREDITCARD,  object_name:IBY_CREDITCARD,  status:VALID,  product: IBY - Paymentsdescription: IBY_CREDITACRD stores Credit Card related information of the customer(payer) or payee. ,  implementation_dba_data: IBY.IBY_CREDITCARD

  • View: IBY_XML_FNDCPT_ORDER_1_0_V 12.1.1

    owner:APPS,  object_type:VIEW,  fnd_design_data:IBY.IBY_XML_FNDCPT_ORDER_1_0_V,  object_name:IBY_XML_FNDCPT_ORDER_1_0_V,  status:VALID,  product: IBY - Paymentsimplementation_dba_data: APPS.IBY_XML_FNDCPT_ORDER_1_0_V

  • View: IBY_XML_FNDCPT_ORDER_1_0_V 12.2.2

    owner:APPS,  object_type:VIEW,  fnd_design_data:IBY.IBY_XML_FNDCPT_ORDER_1_0_V,  object_name:IBY_XML_FNDCPT_ORDER_1_0_V,  status:VALID,  product: IBY - Paymentsimplementation_dba_data: APPS.IBY_XML_FNDCPT_ORDER_1_0_V