Search Results iby_payee




Overview
Explore in AI Chat

Overview

The IBY_PAYEE table is a core data object within the Oracle E-Business Suite Payments (IBY) module, specifically in versions 12.1.1 and 12.2.2. It serves as the master repository for payee information. A payee is defined as any external entity to which the organization makes payments, such as suppliers (billers), merchants, or stores. Each row in this table uniquely identifies a payee at the installation site. The table's primary role is to centralize payee definitions, enabling their association with various payment methods, risk configurations, and transaction processing rules across the Payments module. It is a foundational table that supports the configuration and execution of electronic and printed payment processes.

Key Information Stored

While the provided metadata does not list all columns, the primary and unique key structures reveal critical identifiers. The table uses two key identifiers: the MPAYEEID and the PAYEEID. The MPAYEEID column is the primary key (IBY_PAYEE_PK), serving as the main internal, system-generated identifier for the payee record. The PAYEEID column is governed by a unique key constraint (IBY_PAYEE_UK), representing a distinct business identifier for the payee, likely used for integration and external reference. Another documented column is ECAPPID, which is a foreign key to the IBY_ECAPP table, linking the payee to an Electronic Commerce Application for specific payment processing contexts.

Common Use Cases and Queries

This table is central to payment setup and inquiry operations. Common use cases include configuring payee-specific payment instructions, defining default banking details, and setting up fraud detection rules (IBY Risk Management) for specific merchants. For reporting, it is frequently joined to transaction tables to analyze payment history by payee. A typical query pattern involves joining IBY_PAYEE to transaction summary tables. For example, to list payees with recent payment activity, one might use:

SELECT ip.PAYEEID, ip.MPAYEEID, COUNT(its.TRANSACTION_ID) AS TXN_COUNT
FROM IBY.IBY_PAYEE ip
JOIN IBY.IBY_TRXN_SUMMARIES_ALL its ON ip.MPAYEEID = its.MPAYEEID
WHERE its.TRANSACTION_DATE > SYSDATE - 30
GROUP BY ip.PAYEEID, ip.MPAYEEID;

Another common scenario is querying payee details along with their associated accepted payment methods from the IBY_ACCPPMTMTHD table using the MPAYEEID as the join key.

Related Objects

The IBY_PAYEE table has extensive relationships within the Payments schema, as evidenced by its foreign key constraints. Key related objects include:

  • IBY_ECAPP: Linked via IBY_PAYEE.ECAPPID.
  • IBY_ACCPPMTMTHD: References IBY_PAYEE.MPAYEEID to define payment methods accepted by a payee.
  • IBY_BATCHES_ALL: References IBY_PAYEE.MPAYEEID to associate payment batches with a payee.
  • IBY_DEFAULT_BEP: References IBY_PAYEE.MPAYEEID to store a payee's default payment instruction (Bank Account).
  • IBY_ROUTINGINFO: References IBY_PAYEE.MPAYEEID for payee-specific payment routing details.
  • IBY_TRXN_SUMMARIES_ALL: References IBY_PAYEE.MPAYEEID to summarize transactions per payee.
  • Risk Management Objects: Multiple tables (e.g., IBY_RISK_FORMULAS, IBY_IRF_PMT_AMOUNT) reference IBY_PAYEE.PAYEEID to attach fraud detection rules to specific payees.
  • IBY_PAYEE_SUBKEYS: References IBY_PAYEE.MPAYEE_ID for storing additional payee identifiers.
  • IBY_MAPPINGS: References IBY_PAYEE.PAYEEID for mapping payees to internal entities.
  • Table: IBY_PAYEE 12.1.1

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_PAYEE,  object_name:IBY_PAYEE,  status:VALID,  product: IBY - Payments ,  description: IBY_PAYEE holds a row for each payee such as a biller or merchant/store at this site. ,  implementation_dba_data: IBY.IBY_PAYEE , 

  • Table: IBY_PAYEE 12.2.2

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_PAYEE,  object_name:IBY_PAYEE,  status:VALID,  product: IBY - Payments ,  description: IBY_PAYEE stores a row for each payee, such as a biller, merchant, or store at this site. ,  implementation_dba_data: IBY.IBY_PAYEE , 

  • Table: IBY_TRXN_SUMMARIES_ALL 12.1.1

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_TRXN_SUMMARIES_ALL,  object_name:IBY_TRXN_SUMMARIES_ALL,  status:VALID,  product: IBY - Payments ,  description: IBY_TRXN_SUMMARIES_ALL contains information about each payment request. This table is used for both online and offline payment transactions. The information contained in this table is generic in nature to cover the various payment inst ,  implementation_dba_data: IBY.IBY_TRXN_SUMMARIES_ALL , 

  • Table: IBY_TRXN_SUMMARIES_ALL 12.2.2

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_TRXN_SUMMARIES_ALL,  object_name:IBY_TRXN_SUMMARIES_ALL,  status:VALID,  product: IBY - Payments ,  description: IBY_TRXN_SUMMARIES_ALL contains information about each payment request. This table is used for both online and offline payment transactions. The information contained in this table is generic in nature to cover the various payment inst ,  implementation_dba_data: IBY.IBY_TRXN_SUMMARIES_ALL , 

  • Table: IBY_FNDCPT_PAYEE_APPL 12.1.1

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

  • Table: IBY_PAYEE_SUBKEYS 12.2.2

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

  • Table: IBY_PAYEE_SUBKEYS 12.1.1

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

  • Table: IBY_ACCPPMTMTHD 12.1.1

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_ACCPPMTMTHD,  object_name:IBY_ACCPPMTMTHD,  status:VALID,  product: IBY - Payments ,  description: IBY_ACCPPMTMTHD contains a list of all the payment instrument methods that are accepted by a iPayment. ,  implementation_dba_data: IBY.IBY_ACCPPMTMTHD , 

  • Table: IBY_MAPPINGS 12.1.1

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_MAPPINGS,  object_name:IBY_MAPPINGS,  status:VALID,  product: IBY - Payments ,  description: IBY_MAPPINGS stores mapping of codes with risk scores. Each row includes a code and a value for that code. ,  implementation_dba_data: IBY.IBY_MAPPINGS , 

  • Table: IBY_MAPPINGS 12.2.2

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_MAPPINGS,  object_name:IBY_MAPPINGS,  status:VALID,  product: IBY - Payments ,  description: IBY_MAPPINGS stores mapping of codes with risk scores. Each row includes a code and a value for that code. ,  implementation_dba_data: IBY.IBY_MAPPINGS , 

  • Table: IBY_IRF_PMT_HISTORY 12.1.1

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_IRF_PMT_HISTORY,  object_name:IBY_IRF_PMT_HISTORY,  status:VALID,  product: IBY - Payments ,  description: This table stores information pertaining to the payment history risk factor. The merchant can set up different time ranges which he considers risky. ,  implementation_dba_data: IBY.IBY_IRF_PMT_HISTORY , 

  • Table: IBY_ACCPPMTMTHD 12.2.2

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_ACCPPMTMTHD,  object_name:IBY_ACCPPMTMTHD,  status:VALID,  product: IBY - Payments ,  description: IBY_ACCPPMTMTHD contains a list of all the payment instrument methods that are accepted by a iPayment. ,  implementation_dba_data: IBY.IBY_ACCPPMTMTHD , 

  • Table: IBY_IRF_TRXN_AMT_LIMIT 12.1.1

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_IRF_TRXN_AMT_LIMIT,  object_name:IBY_IRF_TRXN_AMT_LIMIT,  status:VALID,  product: IBY - Payments ,  description: IBY_IRF_TRXN_AMT_LIMITstores information pertaining to the transaction amount limit risk factor. It is a limit on the total amount of payments made using the same instrument in a particular duration. ,  implementation_dba_data: IBY.IBY_IRF_TRXN_AMT_LIMIT , 

  • Table: IBY_ROUTINGINFO 12.1.1

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_ROUTINGINFO,  object_name:IBY_ROUTINGINFO,  status:VALID,  product: IBY - Payments ,  description: IBY_ROUTINGINFO contains information that maps routing rule name (payment method name) with the Back End Payment System. ,  implementation_dba_data: IBY.IBY_ROUTINGINFO , 

  • Table: IBY_ROUTINGINFO 12.2.2

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_ROUTINGINFO,  object_name:IBY_ROUTINGINFO,  status:VALID,  product: IBY - Payments ,  description: IBY_ROUTINGINFO stores information that maps payment method to the payment system and funds capture process profile via conditions. ,  implementation_dba_data: IBY.IBY_ROUTINGINFO , 

  • Table: IBY_IRF_PMT_HISTORY 12.2.2

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_IRF_PMT_HISTORY,  object_name:IBY_IRF_PMT_HISTORY,  status:VALID,  product: IBY - Payments ,  description: This table stores information pertaining to the payment history risk factor. The merchant can set up different time ranges which he considers risky. ,  implementation_dba_data: IBY.IBY_IRF_PMT_HISTORY , 

  • Table: IBY_IRF_TRXN_AMT_LIMIT 12.2.2

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_IRF_TRXN_AMT_LIMIT,  object_name:IBY_IRF_TRXN_AMT_LIMIT,  status:VALID,  product: IBY - Payments ,  description: IBY_IRF_TRXN_AMT_LIMITstores information pertaining to the transaction amount limit risk factor. It is a limit on the total amount of payments made using the same instrument in a particular duration. ,  implementation_dba_data: IBY.IBY_IRF_TRXN_AMT_LIMIT , 

  • Table: IBY_ECAPP 12.1.1

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_ECAPP,  object_name:IBY_ECAPP,  status:VALID,  product: IBY - Payments ,  description: IBY_ECAPP stores information about Electronic Commerce Applications registered with iPayment. Oracle Applications which integrate with iPayment directly - via iPayment Java and PL/SQL API's are treated as EC applications by iPayment. They w ,  implementation_dba_data: IBY.IBY_ECAPP , 

  • Table: IBY_IRF_TIMEOF_PURCHASE 12.1.1

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_IRF_TIMEOF_PURCHASE,  object_name:IBY_IRF_TIMEOF_PURCHASE,  status:VALID,  product: IBY - Payments ,  description: This table stores information pertaining to the time of purchase risk factor. The merchant can setup different time ranges - and associate a risk score of low risk, medium low risk, medium risk , medium high risk and high risk. ,  implementation_dba_data: IBY.IBY_IRF_TIMEOF_PURCHASE , 

  • Table: IBY_ECAPP 12.2.2

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_ECAPP,  object_name:IBY_ECAPP,  status:VALID,  product: IBY - Payments ,  description: IBY_ECAPP stores information about Electronic Commerce Applications registered with iPayment. Oracle Applications which integrate with iPayment directly - via iPayment Java and PL/SQL API's are treated as EC applications by iPayment. They w ,  implementation_dba_data: IBY.IBY_ECAPP , 

  • Table: IBY_IRF_PMT_FREQUENCY 12.1.1

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_IRF_PMT_FREQUENCY,  object_name:IBY_IRF_PMT_FREQUENCY,  status:VALID,  product: IBY - Payments ,  description: This table stores information pertaining to the payment frequency risk factor. It basically has information about the frequency of purchase in the given time frame(duration). This risk fatcor is associated with a risk score - low and high. ,  implementation_dba_data: IBY.IBY_IRF_PMT_FREQUENCY , 

  • Table: IBY_RISK_FORMULAS 12.2.2

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_RISK_FORMULAS,  object_name:IBY_RISK_FORMULAS,  status:VALID,  product: IBY - Payments ,  description: IBY_RISK_FORMULAS stores risk formula retaled information . Risk Formula is used by merchants to evaluate the risk of the customer. This formula could be different for different goods/services offered by the merchants. A Risk Formula may be ,  implementation_dba_data: IBY.IBY_RISK_FORMULAS , 

  • Table: IBY_DEFAULT_BEP 12.2.2

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_DEFAULT_BEP,  object_name:IBY_DEFAULT_BEP,  status:VALID,  product: IBY - Payments ,  description: IBY_DEFAULT_BEP stores information that will allow a payment system account and funds capture process profile to be derived for a transaction should the routing rules fail to yield them. ,  implementation_dba_data: IBY.IBY_DEFAULT_BEP , 

  • Table: IBY_IRF_RISKY_INSTR 12.1.1

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_IRF_RISKY_INSTR,  object_name:IBY_IRF_RISKY_INSTR,  status:VALID,  product: IBY - Payments ,  description: IBY_IRF_RISKY_INSTR stores information pertaining to the risk instrument risk factor. It has information about the merchant who sends the file of risky instruments, the type of instrument and other account information pertaining to the risk ,  implementation_dba_data: IBY.IBY_IRF_RISKY_INSTR , 

  • Table: IBY_IRF_PMT_FREQUENCY 12.2.2

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_IRF_PMT_FREQUENCY,  object_name:IBY_IRF_PMT_FREQUENCY,  status:VALID,  product: IBY - Payments ,  description: This table stores information pertaining to the payment frequency risk factor. It basically has information about the frequency of purchase in the given time frame(duration). This risk fatcor is associated with a risk score - low and high. ,  implementation_dba_data: IBY.IBY_IRF_PMT_FREQUENCY , 

  • Table: IBY_IRF_PMT_AMOUNT 12.2.2

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_IRF_PMT_AMOUNT,  object_name:IBY_IRF_PMT_AMOUNT,  status:VALID,  product: IBY - Payments ,  description: This table stores information pertaining to the payment amount risk factor involved in the payment request. A payment request that has huge amount is possibly a fraudulent payment. But the value of the amount varies from business to busines ,  implementation_dba_data: IBY.IBY_IRF_PMT_AMOUNT , 

  • Table: IBY_IRF_RISKY_INSTR 12.2.2

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_IRF_RISKY_INSTR,  object_name:IBY_IRF_RISKY_INSTR,  status:VALID,  product: IBY - Payments ,  description: IBY_IRF_RISKY_INSTR stores information pertaining to the risk instrument risk factor. It has information about the merchant who sends the file of risky instruments, the type of instrument and other account information pertaining to the risk ,  implementation_dba_data: IBY.IBY_IRF_RISKY_INSTR , 

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

  • View: IBY_BATCHES_ALL_V 12.2.2

    owner:APPS,  object_type:VIEW,  fnd_design_data:IBY.IBY_BATCHES_ALL_V,  object_name:IBY_BATCHES_ALL_V,  status:VALID,  product: IBY - Payments ,  description: View used to work with batch transactions. ,  implementation_dba_data: APPS.IBY_BATCHES_ALL_V , 

  • Table: IBY_DEFAULT_BEP 12.1.1

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_DEFAULT_BEP,  object_name:IBY_DEFAULT_BEP,  status:VALID,  product: IBY - Payments ,  description: IBY_DEFAULT_BEP contains the default Back End Payment System information. Based on the instrument type the payment request gets routed to this Back End Payment System. ,  implementation_dba_data: IBY.IBY_DEFAULT_BEP , 

  • Table: IBY_BATCHES_ALL 12.2.2

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_BATCHES_ALL,  object_name:IBY_BATCHES_ALL,  status:VALID,  product: IBY - Payments ,  description: "This table contains records of the settlement batch information which is updated by system while processing 'Create settlement Batches' program.IBY_BATCHES_ALL stores information about batch operations for credit cards and bank account tra ,  implementation_dba_data: IBY.IBY_BATCHES_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 , 

  • View: IBY_BATCHES_ALL_V 12.1.1

    owner:APPS,  object_type:VIEW,  fnd_design_data:IBY.IBY_BATCHES_ALL_V,  object_name:IBY_BATCHES_ALL_V,  status:VALID,  product: IBY - Payments ,  description: View used to work with batch transactions. ,  implementation_dba_data: APPS.IBY_BATCHES_ALL_V , 

  • Table: IBY_IRF_PMT_AMOUNT 12.1.1

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_IRF_PMT_AMOUNT,  object_name:IBY_IRF_PMT_AMOUNT,  status:VALID,  product: IBY - Payments ,  description: This table stores information pertaining to the payment amount risk factor involved in the payment request. A payment request that has huge amount is possibly a fraudulent payment. But the value of the amount varies from business to busines ,  implementation_dba_data: IBY.IBY_IRF_PMT_AMOUNT , 

  • Table: IBY_IRF_TIMEOF_PURCHASE 12.2.2

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_IRF_TIMEOF_PURCHASE,  object_name:IBY_IRF_TIMEOF_PURCHASE,  status:VALID,  product: IBY - Payments ,  description: This table stores information pertaining to the time of purchase risk factor. The merchant can setup different time ranges - and associate a risk score of low risk, medium low risk, medium risk , medium high risk and high risk. ,  implementation_dba_data: IBY.IBY_IRF_TIMEOF_PURCHASE , 

  • Table: IBY_RISK_FORMULAS 12.1.1

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_RISK_FORMULAS,  object_name:IBY_RISK_FORMULAS,  status:VALID,  product: IBY - Payments ,  description: IBY_RISK_FORMULAS stores risk formula retaled information . Risk Formula is used by merchants to evaluate the risk of the customer. This formula could be different for different goods/services offered by the merchants. A Risk Formula may be ,  implementation_dba_data: IBY.IBY_RISK_FORMULAS , 

  • View: IBY_TRANS_FI_V 12.1.1

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

  • View: IBY_TRANS_FI_V 12.2.2

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

  • View: IBY_TRANS_BANKACCT_V 12.2.2

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

  • View: IBY_TRANS_BANKACCT_V 12.1.1

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

  • View: IBY_XML_FNDCPT_ACCT_1_0_V 12.2.2

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

  • View: IBY_XML_ONLINE_FCI_1_0_V 12.2.2

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

  • View: IBY_XML_FNDCPT_ACCT_1_0_V 12.1.1

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

  • View: IBY_XML_ONLINE_FCI_1_0_V 12.1.1

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