Search Results iby_routinginfo




Overview
Explore in AI Chat

Overview

The IBY_ROUTINGINFO table is a core data object within the Oracle E-Business Suite (EBS) Payments (IBY) module. It serves as the central repository for defining and storing routing rules, which are essential for the payment execution engine. Its primary role is to map a payment method name (functioning as a routing rule identifier) to a specific Back End Payment System (BEP). This mapping determines the external payment processor or banking system that will be used to fulfill a payment instruction, enabling the automated routing of payments based on configurable business logic.

Key Information Stored

The table's structure is designed to establish and maintain the relationship between a routing rule and its execution endpoint. The most critical columns include PAYMENTMETHODID, which is the table's primary key and uniquely identifies the routing rule or payment method. The BEPID column is a foreign key that links to the IBY_BEPINFO table, specifying the exact Back End Payment System (e.g., a specific bank or payment gateway) to be used. Another significant column is MPAYEEID, a foreign key referencing the IBY_PAYEE table, which allows the routing rule to be associated with a specific master payee entity, enabling payee-specific payment routing configurations.

Common Use Cases and Queries

A primary use case involves troubleshooting payment processing issues or validating setup. Administrators often query this table to verify which BEP a given payment method is configured to use. For example, to list all configured routing rules with their associated BEP code and payee, a common query pattern is: SELECT ri.paymentmethodid, bep.bep_code, pe.payee_name FROM iby_routinginfo ri, iby_bepinfo bep, iby_payee pe WHERE ri.bepid = bep.bepid AND ri.mpayeeid = pe.payeeid(+);. This data is also critical for reports analyzing payment channel utilization or auditing the payment method setup. Furthermore, the table is integral during the payment process when the Payments engine selects the appropriate BEP based on the payment method assigned to an invoice or payment instruction.

Related Objects

IBY_ROUTINGINFO maintains key relationships with other fundamental tables in the IBY schema. It directly references two tables via foreign keys: IBY_BEPINFO (via the BEPID column) to define the Back End Payment System, and IBY_PAYEE (via the MPAYEEID column) to optionally link to a master payee. Conversely, it is referenced by the IBY_PMTMTHD_CONDITIONS table, whose PAYMENTMETHODID column is a foreign key to IBY_ROUTINGINFO. This relationship allows for the attachment of detailed conditional logic (conditions) to the base routing rule defined in IBY_ROUTINGINFO, enabling more granular control over payment method selection.

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

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_PMTMTHD_CONDITIONS,  object_name:IBY_PMTMTHD_CONDITIONS,  status:VALID,  product: IBY - Payments ,  description: IBY_PMTMTHD_CONDITIONS contains the conditions for the payment method. Each condition is composed of a parameter, operation and value. The condition is evaluated at runtime to check if the condition is satisfied ,  implementation_dba_data: IBY.IBY_PMTMTHD_CONDITIONS , 

  • 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_BEPINFO 12.2.2

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_BEPINFO,  object_name:IBY_BEPINFO,  status:VALID,  product: IBY - Payments ,  description: IBY_BEPKEYS stores information about the payment systems. ,  implementation_dba_data: IBY.IBY_BEPINFO , 

  • Table: IBY_PMTMTHD_CONDITIONS 12.2.2

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_PMTMTHD_CONDITIONS,  object_name:IBY_PMTMTHD_CONDITIONS,  status:VALID,  product: IBY - Payments ,  description: IBY_PMTMTHD_CONDITIONS stores the conditions for payment methods. Each condition is comprised of a parameter, operation, and value. The condition is evaluated at runtime to determine if the payment system account and funds capture process p ,  implementation_dba_data: IBY.IBY_PMTMTHD_CONDITIONS , 

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

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_BEPINFO,  object_name:IBY_BEPINFO,  status:VALID,  product: IBY - Payments ,  description: IBY_BEPINFO has a row for every BEP(Back End Payment System) configured in system. A BEP is a payment provider such as Cybercash, Verifone etc ,  implementation_dba_data: IBY.IBY_BEPINFO ,