Search Results supplier_payment




Overview
Explore in AI Chat

Overview

The IBY_EXT_PARTY_PMT_MTHDS table is a core data repository within the Oracle Payments (IBY) module of Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2. It serves as the central table for storing and managing the payment method preferences of external trading partners, such as suppliers (payees) and customers (payers). Its primary role is to define which payment methods (e.g., Electronic Funds Transfer, Check, Wire) are applicable, and potentially primary, for a specific party, payment function, and payment flow combination. This table is fundamental to both fund disbursement (e.g., supplier payments) and funds capture (e.g., customer receipts) processes, enabling the system to determine the correct payment instrument based on the party's configured preferences.

Key Information Stored

The table's columns define the complex relationships governing payment method applicability. The EXT_PMT_PARTY_ID identifies the external party, while PAYMENT_FLOW (DISBURSEMENTS or FUND_CAPTURE) and PAYMENT_FUNCTION (e.g., SUPPLIER_PAYMENT, CUSTOMER_REFUNDS) establish the transaction context. The applicable instrument is stored in PAYMENT_METHOD_CODE. The PRIMARY_FLAG (Y/N) designates the default method when multiple are applicable. The INACTIVE_DATE allows for the soft deletion of a method preference. The table is uniquely identified by the system-generated primary key EXT_PARTY_PMT_MTHD_ID and maintains standard audit (WHO) columns and an OBJECT_VERSION_NUMBER for data integrity.

Common Use Cases and Queries

A primary use case is determining the valid payment methods for a supplier during a pay run setup. For example, an AP manager may need to report on all active, primary payment methods for suppliers. Another common scenario involves troubleshooting payment formatting errors by verifying the exact payment method code and its status for a specific payee.

  • Sample Query: Find primary payment method for a specific supplier (party) for disbursements:
    SELECT payment_method_code, inactive_date FROM iby.iby_ext_party_pmt_mthds WHERE ext_pmt_party_id = &party_id AND payment_flow = 'DISBURSEMENTS' AND payment_function = 'SUPPLIER_PAYMENT' AND primary_flag = 'Y' AND (inactive_date IS NULL OR inactive_date > SYSDATE);
  • Sample Query: List all payment methods configured for a party site or organization (requires joins to related tables like IBY_EXTERNAL_PAYEES_ALL):
    SELECT ep.party_name, pm.payment_method_code, pm.primary_flag FROM iby.iby_ext_party_pmt_mthds pm, iby.iby_external_payees_all ep WHERE pm.ext_pmt_party_id = ep.ext_payee_id AND pm.payment_flow = 'DISBURSEMENTS' AND ep.payee_party_id = &supplier_party_id;

Related Objects

The IBY_EXT_PARTY_PMT_MTHDS table integrates closely with other IBY and trading partner entities. Its EXT_PMT_PARTY_ID column is a foreign key to party identifiers in tables such as IBY_EXTERNAL_PAYEES_ALL (for disbursements) and IBY_PAYERS_ALL (for funds capture). The PAYMENT_METHOD_CODE references codes in the IBY_PAYMENT_METHODS_TL table. The non-unique indexes (N1, N2) on these columns optimize these critical joins. The table's unique constraint (U1) on the primary key ensures data integrity for any dependent processes or user interfaces that manage these payment method assignments.

  • TABLE: IBY.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, 

  • TABLE: IBY.IBY_TEMP_PMT_INSTR_USES 12.2.2

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_TEMP_PMT_INSTR_USES,  object_name:IBY_TEMP_PMT_INSTR_USES,  status:VALID, 

  • TABLE: IBY.IBY_TEMP_PMT_INSTR_USES 12.1.1

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_TEMP_PMT_INSTR_USES,  object_name:IBY_TEMP_PMT_INSTR_USES,  status:VALID, 

  • TABLE: IBY.IBY_UPG_INSTRUMENTS 12.2.2

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_UPG_INSTRUMENTS,  object_name:IBY_UPG_INSTRUMENTS,  status:VALID, 

  • TABLE: IBY.IBY_UPG_INSTRUMENTS 12.1.1

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_UPG_INSTRUMENTS,  object_name:IBY_UPG_INSTRUMENTS,  status:VALID, 

  • TABLE: IBY.IBY_EXT_PARTY_PMT_MTHDS 12.1.1

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_EXT_PARTY_PMT_MTHDS,  object_name:IBY_EXT_PARTY_PMT_MTHDS,  status:VALID, 

  • TABLE: IBY.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, 

  • TABLE: IBY.IBY_PAY_INSTRUCTIONS_H 12.2.2

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_PAY_INSTRUCTIONS_H,  object_name:IBY_PAY_INSTRUCTIONS_H,  status:VALID, 

  • TABLE: IBY.IBY_PAY_INSTRUCTIONS_H 12.1.1

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_PAY_INSTRUCTIONS_H,  object_name:IBY_PAY_INSTRUCTIONS_H,  status:VALID, 

  • TABLE: IBY.IBY_GEN_DOCS_PAYABLE 12.2.2

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_GEN_DOCS_PAYABLE,  object_name:IBY_GEN_DOCS_PAYABLE,  status:VALID, 

  • TABLE: IBY.IBY_GEN_DOCS_PAYABLE 12.1.1

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_GEN_DOCS_PAYABLE,  object_name:IBY_GEN_DOCS_PAYABLE,  status:VALID, 

  • TABLE: IBY.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, 

  • TABLE: IBY.IBY_DOCUMENTS_PAYABLE_H 12.2.2

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_DOCUMENTS_PAYABLE_H,  object_name:IBY_DOCUMENTS_PAYABLE_H,  status:VALID, 

  • TABLE: IBY.IBY_PAY_INSTRUCTIONS_ALL 12.2.2

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_PAY_INSTRUCTIONS_ALL,  object_name:IBY_PAY_INSTRUCTIONS_ALL,  status:VALID, 

  • TABLE: IBY.IBY_PAY_INSTRUCTIONS_ALL 12.1.1

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_PAY_INSTRUCTIONS_ALL,  object_name:IBY_PAY_INSTRUCTIONS_ALL,  status:VALID, 

  • TABLE: IBY.IBY_DOCUMENTS_PAYABLE_H 12.1.1

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_DOCUMENTS_PAYABLE_H,  object_name:IBY_DOCUMENTS_PAYABLE_H,  status:VALID, 

  • TABLE: IBY.IBY_PAYMENTS_H 12.1.1

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_PAYMENTS_H,  object_name:IBY_PAYMENTS_H,  status:VALID, 

  • TABLE: IBY.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, 

  • TABLE: IBY.IBY_PAYMENTS_H 12.2.2

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_PAYMENTS_H,  object_name:IBY_PAYMENTS_H,  status:VALID, 

  • TABLE: IBY.IBY_DOCS_PAYABLE_ALL 12.1.1

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_DOCS_PAYABLE_ALL,  object_name:IBY_DOCS_PAYABLE_ALL,  status:VALID, 

  • TABLE: IBY.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, 

  • TABLE: IBY.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, 

  • eTRM - IBY Tables and Views 12.1.1

    description: Stores the user privilege settings for viewing sensitive data in iPayment operations UI , 

  • eTRM - IBY Tables and Views 12.2.2

    description: Stores the user privilege settings for viewing sensitive data in iPayment operations UI ,