Search Results iby_external_payees_all




The IBY_EXTERNAL_PAYEES_ALL table is a critical component within Oracle E-Business Suite (EBS) Release 12.1.1 and 12.2.2, specifically designed to support the Oracle Payments module. This table serves as a repository for storing detailed information about external payees—entities or individuals outside the organization who receive payments. It plays a pivotal role in payment processing, enabling organizations to manage vendor, employee, and other third-party payment details efficiently. Below is a detailed exploration of its structure, functionality, and significance in Oracle EBS.

Purpose and Context

The IBY_EXTERNAL_PAYEES_ALL table is part of the Oracle Payments module, which centralizes payment processing across Oracle EBS applications like Accounts Payable (AP), Payroll, and Treasury. It stores master data for payees who are not internal employees or system users but are recipients of payments (e.g., suppliers, contractors, or beneficiaries). This table ensures consistency in payee information across modules, reducing duplication and errors.

Key Columns and Structure

The table includes columns to capture comprehensive payee details, such as:
  • EXT_PAYEE_ID: Primary key, uniquely identifying each payee record.
  • PAYEE_PARTY_ID: References the party in Oracle Trading Community Architecture (TCA), linking payees to broader entity management.
  • PAYMENT_FUNCTION: Defines the payee's role (e.g., "VENDOR" for suppliers or "EMPLOYEE" for external workers).
  • ORG_ID: Supports multi-org structures by segregating data by operating unit.
  • BANK_ACCOUNT_ID: Links to IBY_EXT_BANK_ACCOUNTS, storing bank details for electronic payments.
  • CREATION_DATE, LAST_UPDATE_DATE: Audit columns tracking record lifecycle.

Integration with Other Modules

IBY_EXTERNAL_PAYEES_ALL integrates with:
  • Oracle TCA: Uses HZ_PARTIES to maintain party relationships.
  • AP Suppliers: Maps to PO_VENDORS for supplier payments.
  • Payroll: Connects to PER_ALL_PEOPLE_F for employee-related payees.
  • Bank Account Management: References IBY_EXT_BANK_ACCOUNTS for payment instructions.

Functional Significance

This table enables:
  • Centralized Payee Management: Eliminates redundant payee records across modules.
  • Payment Flexibility: Supports multiple payment methods (EFT, checks) per payee.
  • Compliance: Stores tax identifiers (e.g., VAT, TIN) for regulatory reporting.
  • Auditability: Tracks changes for SOX and internal controls.

Technical Considerations

In EBS 12.2.2, the table benefits from Oracle's Online Patching (ADOP) for maintenance. Indexes on EXT_PAYEE_ID, PAYEE_PARTY_ID, and ORG_ID optimize query performance. Customizations should avoid direct DML, leveraging Oracle APIs like IBY_PAYEE_API to ensure data integrity.

Conclusion

The IBY_EXTERNAL_PAYEES_ALL table is foundational to Oracle Payments, providing a unified model for external payee data. Its design aligns with Oracle's modular architecture, ensuring seamless integration with financial and supply chain processes. Proper utilization of this table enhances payment accuracy, reduces administrative overhead, and supports compliance—making it indispensable for organizations running Oracle EBS 12.1.1 or 12.2.2.

  • 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_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_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_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_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_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_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 , 

  • 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 ,