Supplier Payment Method

In Oracle on the supplier/supplier site a payment method can be maintained. e.g.  CHECK or EFT.
When the Supplier is created the payment method information is populated in the table :
IBY_EXTERNAL_PAYEES_ALL and IBY_EXT_PARTY_PMT_MTHDS

Post creation when the payment method details are updated oracle will insert a new record in the table : IBY_EXT_PARTY_PMT_MTHDS , thus this table maitains the complete history of payment method details of the supplier/supplier site.

The current record is identified by PRIMARY_FLAG = 'Y' .

select

aps.vendor_name,aps.segment1 ,asl.vendor_site_code,pmt.PAYMENT_METHOD_CODE

from apps.ap_suppliers aps,
apps.ap_supplier_sites_all asl,
apps.IBY_EXTERNAL_PAYEES_ALL iep,
APPS.IBY_EXT_PARTY_PMT_MTHDS pmt
where aps.vendor_id = asl.vendor_id
and asl.vendor_site_id = iep.supplier_site_id
and asl.org_id = iep.org_id
and iep.ext_payee_id = pmt.ext_pmt_party_id
and pmt.primary_flag = 'Y'

Supplier Payment Methods in Oracle

In Oracle, whenever a  supplier or supplier site is Created in oracle , Oracle will automatically create a payee in the system and depending on the data provided a payment method.

Each payee will define the different attributes which are related to all the aspects of payments for that supplier or supplier site.

For each supplier or supplier site the business might want to define the payment methods i.e. mechanism in which the payment will be made, this might the EFT,WIRE,CHECK etc.

When creating a supplier the API will automatically create the payee and payment method for the supplier will be created, provided a payment method is passed to the API . If we pass NULL to the API in the payment method then no payment method will be created.

Even if the payment method is created in the system but if the PRIMARY_FLAG = 'N' then this payment method will not be visible in the front end.