Search Results iby_external_payees_all




Overview
Explore in AI Chat

Overview

The IBY_EXTERNAL_PAYEES_ALL table is a core repository within the Oracle Payments (IBY) module of Oracle E-Business Suite (EBS) versions 12.1.1 and 12.2.2. It serves as the master table for storing information about external payees, which are individuals or entities outside the organization who receive payments. This includes suppliers, employees, contractors, and other beneficiaries. The table's primary role is to centralize and maintain the detailed payment instructions and preferences for each payee, enabling the accurate and efficient processing of electronic and manual payments. Its 'ALL' suffix indicates it is a multi-organization table, storing data partitioned by the ORG_ID column for use in a Multi-Org environment.

Key Information Stored

The table's structure is designed to capture comprehensive payment details. Its primary key is the EXT_PAYEE_ID, a unique system-generated identifier. Key columns include PAYEE_PARTY_ID, which links to the Trading Community Architecture (TCA) party record, and PAYEE_NAME. Critical payment instruction columns are DEFAULT_PAYMENT_METHOD_CODE (linking to IBY_PAYMENT_METHODS_B), DELIVERY_CHANNEL_CODE (linking to IBY_DELIVERY_CHANNELS_B), and PAYMENT_FORMAT_CODE. The table also stores specific banking instructions and payment reason codes via BANK_INSTRUCTION1_CODE, BANK_INSTRUCTION2_CODE, and PAYMENT_REASON_CODE. The ORG_ID column is essential for data segregation in Multi-Org implementations.

Common Use Cases and Queries

This table is central to payment setup and inquiry processes. Common use cases include validating payee payment instructions before running a payment process, reporting on all payees configured for a specific payment method or delivery channel, and troubleshooting payment failures by examining a payee's setup. A typical query retrieves a payee's complete payment instructions:

  • SELECT payee_name, default_payment_method_code, delivery_channel_code, payment_format_code FROM iby_external_payees_all WHERE ext_payee_id = :payee_id AND org_id = :org_id;

Another common pattern joins with the TCA layer to get a comprehensive list:

  • SELECT iep.payee_name, iep.default_payment_method_code, hp.party_name FROM iby_external_payees_all iep, hz_parties hp WHERE iep.payee_party_id = hp.party_id AND iep.org_id = :org_id;

Related Objects

IBY_EXTERNAL_PAYEES_ALL is a central hub with several key relationships. It is referenced by the FV_TPP_ASSIGNMENTS_ALL table for Third-Party Payment assignments and by the IBY_PAYMENTS_ALL table, which stores individual payment records. As indicated by its foreign keys, it draws valid values from critical look-up and setup tables: IBY_PAYMENT_METHODS_B, IBY_DELIVERY_CHANNELS_B, and internal code tables for bank instructions and payment reasons. The table is fundamentally linked to the Oracle Trading Community Architecture (TCA) via the PAYEE_PARTY_ID foreign key to HZ_PARTIES, ensuring a single source of truth for entity data.

  • 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_EXTERNAL_PAYEES_ALL 12.1.1

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_EXTERNAL_PAYEES_ALL,  object_name:IBY_EXTERNAL_PAYEES_ALL,  status:VALID,  product: IBY - Payments ,  implementation_dba_data: IBY.IBY_EXTERNAL_PAYEES_ALL , 

  • Table: IBY_BANK_INSTRUCTIONS_B 12.2.2

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_BANK_INSTRUCTIONS_B,  object_name:IBY_BANK_INSTRUCTIONS_B,  status:VALID,  product: IBY - Payments ,  description: IBY_BANK_INSTRUCTIONS stores bank instructions that are used as lookup values for payment process profiles and external payee setup. This table corresponds to the Bank Instruction Codes page. ,  implementation_dba_data: IBY.IBY_BANK_INSTRUCTIONS_B , 

  • View: IBY_EXTERNAL_PAYEES_V 12.2.2

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

  • Table: IBY_PAYMENTS_ALL 12.1.1

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_PAYMENTS_ALL,  object_name:IBY_PAYMENTS_ALL,  status:VALID,  product: IBY - Payments ,  implementation_dba_data: IBY.IBY_PAYMENTS_ALL , 

  • Table: IBY_PAYMENT_METHODS_B 12.1.1

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_PAYMENT_METHODS_B,  object_name:IBY_PAYMENT_METHODS_B,  status:VALID,  product: IBY - Payments ,  implementation_dba_data: IBY.IBY_PAYMENT_METHODS_B , 

  • Table: IBY_DELIVERY_CHANNELS_B 12.1.1

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_DELIVERY_CHANNELS_B,  object_name:IBY_DELIVERY_CHANNELS_B,  status:VALID,  product: IBY - Payments ,  implementation_dba_data: IBY.IBY_DELIVERY_CHANNELS_B , 

  • Table: IBY_PAYMENT_METHODS_B 12.2.2

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_PAYMENT_METHODS_B,  object_name:IBY_PAYMENT_METHODS_B,  status:VALID,  product: IBY - Payments ,  description: IBY_PAYMENT_METHODS stores the payment methods that Oracle Payments supports. A payment method is a payment attribute on a document payable that indicates how the first party payer is going to make the payment. Examples of payment methods i ,  implementation_dba_data: IBY.IBY_PAYMENT_METHODS_B , 

  • Table: IBY_DELIVERY_CHANNELS_B 12.2.2

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_DELIVERY_CHANNELS_B,  object_name:IBY_DELIVERY_CHANNELS_B,  status:VALID,  product: IBY - Payments ,  description: IBY_DELIVERY_CHANNELS stores delivery channel information that is used as lookup values for external payee setup or documents payable. The table is similar to FND_LOOKUPS, but with a new column for territory identification. Products that us ,  implementation_dba_data: IBY.IBY_DELIVERY_CHANNELS_B , 

  • View: IBY_EXTERNAL_PAYEES_V 12.1.1

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

  • Table: IBY_EXT_PARTY_PMT_MTHDS 12.2.2

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_EXT_PARTY_PMT_MTHDS,  object_name:IBY_EXT_PARTY_PMT_MTHDS,  status:VALID,  product: IBY - Payments ,  description: IBY_EXT_PARTY_PMT_MTHDS stores payment method applicability driven by the preferences of the external party. A payment method is applicable to a party and payment function combination and, optionally and additionally, to a party site and/or ,  implementation_dba_data: IBY.IBY_EXT_PARTY_PMT_MTHDS , 

  • Table: IBY_DOCS_PAYABLE_ALL 12.2.2

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_DOCS_PAYABLE_ALL,  object_name:IBY_DOCS_PAYABLE_ALL,  status:VALID,  product: IBY - Payments ,  description: "This table contains records of the documents payable which are updated by system while processing 'Build payments' program. IBY_DOCS_PAYABLE_ALL stores Oracle Payments' representation of source products' documents payable. A document pay ,  implementation_dba_data: IBY.IBY_DOCS_PAYABLE_ALL , 

  • Table: IBY_PAYMENT_REASONS_B 12.2.2

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_PAYMENT_REASONS_B,  object_name:IBY_PAYMENT_REASONS_B,  status:VALID,  product: IBY - Payments ,  description: IBY_PAYMENT_REASONS stores payment reasons that are used as lookup values for payee records or documents payable, that is, invoices. This table is similar to FND_LOOKUPS, but with a new column for territory identification. Products that use ,  implementation_dba_data: IBY.IBY_PAYMENT_REASONS_B , 

  • View: IBY_PAYEE_ASSIGNED_BANKACCT_V 12.2.2

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

  • View: IBY_PAYEE_ASSIGNED_BANKACCT_V 12.1.1

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

  • Table: IBY_PAYMENTS_ALL 12.2.2

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_PAYMENTS_ALL,  object_name:IBY_PAYMENTS_ALL,  status:VALID,  product: IBY - Payments ,  description: "This table contains records of the payments which are created by system while processing 'Build payments' program. A payment can be a single check or an electronic fund transfer between first party payer and third party payee. A row in ,  implementation_dba_data: IBY.IBY_PAYMENTS_ALL , 

  • Table: IBY_FORMATS_B 12.2.2

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_FORMATS_B,  object_name:IBY_FORMATS_B,  status:VALID,  product: IBY - Payments ,  description: Stores payment processing format types ,  implementation_dba_data: IBY.IBY_FORMATS_B ,