Search Results iby_default_bep




Overview
Explore in AI Chat

Overview

The IBY_DEFAULT_BEP table is a core data object within the Oracle E-Business Suite (EBS) Payments (IBY) module. Its primary function is to provide a fallback mechanism for payment processing. When the application of complex routing rules fails to determine a suitable payment system account or a funds capture process profile for a given transaction, this table supplies the necessary default configuration. This ensures that payment processing can proceed without interruption, maintaining operational continuity in scenarios where specific routing criteria are not met. The table is integral to the payment engine's decision-making logic, serving as a critical safety net within the financial transaction flow for both releases 12.1.1 and 12.2.2.

Key Information Stored

The table stores the relationships and identifiers required to derive default payment processing entities. Its structure is defined by a composite primary key and several foreign key relationships. The primary key, IBY_DEFAULT_BEP_UK, consists of the BEPID (Banking Entity Participant ID) and the INSTRTYPE (Instrument Type), ensuring a unique default record per payment method and participant. Key columns include BEPID, which identifies the payment system or banking entity; INSTRTYPE, which specifies the payment instrument (e.g., wire, check); MPAYEEID, which links to a master payee record in IBY_PAYEE; and BEP_ACCOUNT_ID, which references a specific account for the banking entity within IBY_BEPKEYS. Together, these columns define the default payment pathway.

Common Use Cases and Queries

A primary use case is troubleshooting payment transactions that have utilized default routing. Administrators may query this table to verify or audit the fallback configuration for a specific payment method and banking entity. Common SQL patterns involve joining to related reference tables to obtain descriptive information. For example, to list all default configurations with their associated payee names, one might use:

  • SELECT db.BEPID, db.INSTRTYPE, p.PAYEE_NAME FROM IBY_DEFAULT_BEP db, IBY_PAYEE p WHERE db.MPAYEEID = p.PAYEEID(+);

Another critical scenario is during implementation or upgrades, where ensuring the existence of correct default entries is essential for payment process stability. Reporting use cases focus on documenting the fallback setup for compliance and process documentation.

Related Objects

The IBY_DEFAULT_BEP table maintains defined foreign key relationships with several core IBY tables, as documented in the ETRM metadata. These relationships are fundamental to its integrity and purpose:

  • IBY_BEPINFO: The BEPID column references IBY_BEPINFO, linking the default to detailed banking entity information.
  • IBY_PAYEE: The MPAYEEID column references IBY_PAYEE, associating the default routing with a specific master payee record.
  • IBY_BEPKEYS: The BEP_ACCOUNT_ID column references IBY_BEPKEYS, connecting to the specific account details for the banking entity.

These relationships ensure that the default configuration points to valid, existing entities within the payment ecosystem.

  • 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_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_BEPKEYS 12.1.1

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_BEPKEYS,  object_name:IBY_BEPKEYS,  status:VALID,  product: IBY - Payments ,  description: IBY_BEPKEYS contains a list of all the keys that identifies a payee or payer with a Back End Payment System. ,  implementation_dba_data: IBY.IBY_BEPKEYS , 

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

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

  • View: IBY_F_LENDERS_V 12.1.1

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

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

  • View: IBY_F_LENDERS_V 12.2.2

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