Search Results supplier payees




The IBY_INSTRHOLDER table in Oracle E-Business Suite (EBS) versions 12.1.1 and 12.2.2 serves as a critical repository for storing instrument holder information within the Oracle Payments module. This table is part of the broader Oracle Payments infrastructure, which facilitates payment processing across multiple Oracle applications, including Accounts Payable (AP), Accounts Receivable (AR), and Treasury. The IBY_INSTRHOLDER table primarily stores details about entities (individuals or organizations) that hold payment instruments such as bank accounts, credit cards, or other financial instruments used in electronic transactions. ### **Key Attributes of IBY_INSTRHOLDER** The table contains several important columns that define the instrument holder's relationship with payment instruments: 1. **INSTR_HOLDER_ID**: A unique identifier for each instrument holder, serving as the primary key. 2. **HOLDER_TYPE**: Specifies whether the holder is an individual (PERSON) or an organization (ORGANIZATION). 3. **HOLDER_NAME**: The legal name of the instrument holder (e.g., a person’s full name or a company name). 4. **HOLDER_REFERENCE**: An optional reference identifier, often used for internal tracking. 5. **CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE**: Standard Oracle EBS audit columns tracking record creation and modification. 6. **OBJECT_VERSION_NUMBER**: Used for optimistic locking to prevent concurrent updates. ### **Functional Role in Oracle Payments** The IBY_INSTRHOLDER table acts as a central reference for payment instrument ownership. It links to other key tables in the Oracle Payments schema, such as: - **IBY_INSTRUMENTS_ALL**: Stores payment instrument details (bank accounts, credit cards), referencing INSTR_HOLDER_ID to associate instruments with their holders. - **IBY_EXTERNAL_PAYEES_ALL**: Maps external payees (suppliers, customers) to instrument holders for payment processing. - **IBY_PMT_INSTR_USES_ALL**: Tracks instrument usage across payment transactions. ### **Integration with Oracle EBS Modules** 1. **Accounts Payable (AP)**: When suppliers are paid electronically, their bank account details are stored in IBY_INSTRUMENTS_ALL, with the supplier’s legal entity referenced in IBY_INSTRHOLDER. 2. **Accounts Receivable (AR)**: Customer payment methods (e.g., direct debit mandates) rely on instrument holder data to validate transactions. 3. **Treasury (CE)**: Cash management uses instrument holder data to reconcile bank statements with internal records. ### **Data Flow and Maintenance** - **Creation**: Instrument holders are typically created automatically when payment instruments are registered (e.g., via Supplier or Customer onboarding). - **Updates**: Changes to holder details (e.g., legal name updates) propagate to linked instruments and transactions. - **Deletion**: Constraints prevent deletion if active instruments or transactions reference the holder. ### **Technical Considerations** - **Indexing**: The INSTR_HOLDER_ID is indexed for performance in joins with related tables. - **Security**: Access is restricted via Oracle Payments’ security model (e.g., IBY_ACCESS_SETUP). - **Custom Extensions**: Customizations should avoid direct DML on this table to prevent integrity issues. ### **Conclusion** The IBY_INSTRHOLDER table is a foundational component of Oracle Payments, ensuring accurate and auditable instrument ownership across financial transactions. Its design supports scalability, referential integrity, and seamless integration with core EBS modules, making it indispensable for organizations leveraging Oracle’s payment processing capabilities.

  • Lookup Type: IBY_OAUI_SEC_VIS_DTL_ALL_ENTRY 12.1.1

    product: IBY - Payments ,  meaning: IBY_OAUI_SEC_VIS_DTL_ALL_ENTRY ,  description: Translatable display strings for all payees, organizations and EC applications , 

  • Lookup Type: IBY_OAUI_SEC_VIS_DTL_ALL_ENTRY 12.2.2

    product: IBY - Payments ,  meaning: IBY_OAUI_SEC_VIS_DTL_ALL_ENTRY ,  description: Translatable display strings for all payees, organizations and EC applications , 

  • Lookup Type: IBY_DELIVERY_METHODS 12.1.1

    product: IBY - Payments ,  meaning: Delivery Methods ,  description: Defines delivery methods that can be used to deliver remittance advice to payees , 

  • 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 - Payments ,  description: 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.2.2

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_INSTRHOLDER,  object_name:IBY_INSTRHOLDER,  status:VALID,  product: IBY - Payments ,  description: 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_FNDCPT_PAYEE_APPL 12.2.2

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_FNDCPT_PAYEE_APPL,  object_name:IBY_FNDCPT_PAYEE_APPL,  status:VALID,  product: IBY - Payments ,  description: IBY_FNDCPT_PAYEE_APPL is a mapping table between internal payees and operating units. One payee may be associated with many operating units. An operating unit may be associated with at most one payee. ,  implementation_dba_data: IBY.IBY_FNDCPT_PAYEE_APPL , 

  • Lookup Type: IBY_DELIVERY_METHODS 12.2.2

    product: IBY - Payments ,  meaning: Delivery Methods ,  description: Defines delivery methods that can be used to deliver remittance advice to payees , 

  • Table: IBY_PMT_INSTR_USES_ALL 12.2.2

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_PMT_INSTR_USES_ALL,  object_name:IBY_PMT_INSTR_USES_ALL,  status:VALID,  product: IBY - Payments ,  description: "This table contains records of the relationship between payment instruments and Payer/Payee. Data can be entered manually. IBY_PMT_INSTR_USES_ALL table assigns payment instruments to external party payers and payees. This table is shared ,  implementation_dba_data: IBY.IBY_PMT_INSTR_USES_ALL , 

  • Table: IBY_BATCHES_ALL 12.1.1

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_BATCHES_ALL,  object_name:IBY_BATCHES_ALL,  status:VALID,  product: IBY - Payments ,  description: IBY_BATCHES holds the information about batch operations for SSL credit card transactions. A terminal based merchant will need to have batch operations. The status of the payees batch will be contained in this table. ,  implementation_dba_data: IBY.IBY_BATCHES_ALL , 

  • Lookup Type: IBY_FIN_TRADE_REF_TYPES 12.1.1

    product: IBY - Payments ,  meaning: IBY_FIN_TRADE_REF_TYPES ,  description: Financing Trade Reference Types , 

  • Lookup Type: IBY_FIN_TRADE_REF_TYPES 12.2.2

    product: IBY - Payments ,  meaning: IBY_FIN_TRADE_REF_TYPES ,  description: Financing Trade Reference Types , 

  • Table: IBY_EXTERNAL_PAYEES_ALL 12.2.2

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_EXTERNAL_PAYEES_ALL,  object_name:IBY_EXTERNAL_PAYEES_ALL,  status:VALID,  product: IBY - Payments ,  description: "This table contains payment details of an external payee automatically created by the source product. For example when supplier or supplier site is created manually system automatically inserts row in to the IBY_EXTERNAL_PAYEES_ALL table. ,  implementation_dba_data: IBY.IBY_EXTERNAL_PAYEES_ALL , 

  • Table: IBY_EXT_PAYEE_RELATIONSHIPS 12.2.2

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_EXT_PAYEE_RELATIONSHIPS,  object_name:IBY_EXT_PAYEE_RELATIONSHIPS,  status:VALID,  product: IBY - Payments ,  description: "This table stores information about third party payment related relationships and related attributes. IBY_EXT_PAYEE_RELATIONSHIPS contain third payment relationships entered manually using the Relationship region in the supplier page. Eac ,  implementation_dba_data: IBY.IBY_EXT_PAYEE_RELATIONSHIPS , 

  • Table: IBY_ACCOUNT_OWNERS 12.2.2

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_ACCOUNT_OWNERS,  object_name:IBY_ACCOUNT_OWNERS,  status:VALID,  product: IBY - Payments ,  description: This table contains records of the account owners of the external bank accounts entered manually. This table corresponds to the Banking details page of supplier or customer. When an external bank account is created a row will be stored in ,  implementation_dba_data: IBY.IBY_ACCOUNT_OWNERS , 

  • Table: IBY_EXT_BANK_ACCOUNTS 12.2.2

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_EXT_BANK_ACCOUNTS,  object_name:IBY_EXT_BANK_ACCOUNTS,  status:VALID,  product: IBY - Payments ,  description: "This table contains records of the external bank accounts entered manually. This table corresponds to the Banking details page of supplier or customer. This table contains bank, branch, masking, encryption details of the external bank acc ,  implementation_dba_data: IBY.IBY_EXT_BANK_ACCOUNTS , 

  • View: IBY_EXT_FD_PAYEE_1_0_V 12.1.1

    owner:APPS,  object_type:VIEW,  fnd_design_data:IBY.IBY_EXT_FD_PAYEE_1_0_V,  object_name:IBY_EXT_FD_PAYEE_1_0_V,  status:VALID,  product: IBY - Payments ,  implementation_dba_data: APPS.IBY_EXT_FD_PAYEE_1_0_V , 

  • View: IBY_EXT_FD_PAYEE_1_0_V 12.2.2

    owner:APPS,  object_type:VIEW,  fnd_design_data:IBY.IBY_EXT_FD_PAYEE_1_0_V,  object_name:IBY_EXT_FD_PAYEE_1_0_V,  status:VALID,  product: IBY - Payments ,  implementation_dba_data: APPS.IBY_EXT_FD_PAYEE_1_0_V ,