Search Results iby_bepinfo

Overview

The IBY_BEPINFO table is a core master data table within the Oracle E-Business Suite Payments (IBY) module. It serves as the central repository for all configured Back End Payment (BEP) systems. A BEP represents an external payment provider or financial institution, such as Cybercash or Verifone, which processes electronic payments like EFT, EDI, or wire transfers. Each row in this table defines a unique payment system available for processing transactions, making it fundamental to the setup and operation of the Oracle Payments engine in both EBS 12.1.1 and 12.2.2.

Key Information Stored

The table's primary identifier is the BEPID column, which is the primary key (IBY_BEPINFO_PK). Two other columns are enforced as unique keys, ensuring critical business rules: the NAME (IBY_BEP_NAME_UK) and the SUFFIX (IBY_BEP_SUFFIX_UK). The table maintains relationships with external entities through foreign keys. The PARTY_ID column links to HZ_PARTIES, associating the BEP with a party record in Trading Community Architecture. Similarly, the BANK_ID column links to HZ_PARTIES to identify the specific bank institution associated with this payment system. This structure allows the system to manage the complete business entity details of each payment provider.

Common Use Cases and Queries

This table is primarily referenced for configuration validation, reporting on available payment systems, and troubleshooting payment processing flows. Common queries include listing all active BEPs for a given payment method or identifying the BEP associated with a specific bank. For instance, to retrieve all configured BEPs with their associated bank party names, a join to HZ_PARTIES is typical:

SELECT bip.NAME, bip.SUFFIX, hp.PARTY_NAME FROM IBY.IBY_BEPINFO bip, HZ_PARTIES hp WHERE bip.BANK_ID = hp.PARTY_ID;

Another critical use case is verifying the BEP setup for a problematic payment instruction or batch, often by joining to transactional tables like IBY_PAY_INSTRUCTIONS_H or IBY_BATCHES_ALL on the BEPID column to diagnose routing or formatting errors.

Related Objects

IBY_BEPINFO is a parent table to numerous key objects in the Payments schema, as evidenced by its extensive foreign key relationships. Major child tables include:

IBY_BATCHES_ALL: Stores payment batches processed through a BEP.
IBY_PAY_INSTRUCTIONS_H: Holds payment instructions assigned to a BEP.
IBY_PMTSCHEMES and IBY_PMT_SYS_FORMATS: Define payment methods and file formats for the BEP.
IBY_SYS_PMT_PROFILES_B: Contains system payment profiles linked to a BEP.
IBY_TRXN_SUMMARIES_ALL: Stores transaction summaries for each BEP.
IBY_BEPKEYS and IBY_BEPLANGS: Store security keys and language-specific translations for the BEP, respectively.

These relationships underscore that IBY_BEPINFO is the anchor point for all configuration and transactional data pertaining to a specific payment processing system.

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 ,
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_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_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_PMT_SYS_TRANSMISSIONS 12.1.1
owner:IBY, object_type:TABLE, fnd_design_data:IBY.IBY_PMT_SYS_TRANSMISSIONS, object_name:IBY_PMT_SYS_TRANSMISSIONS, status:VALID, product: IBY - Payments , implementation_dba_data: IBY.IBY_PMT_SYS_TRANSMISSIONS ,
Table: IBY_PMT_SYS_TRANSMISSIONS 12.2.2
owner:IBY, object_type:TABLE, fnd_design_data:IBY.IBY_PMT_SYS_TRANSMISSIONS, object_name:IBY_PMT_SYS_TRANSMISSIONS, status:VALID, product: IBY - Payments , implementation_dba_data: IBY.IBY_PMT_SYS_TRANSMISSIONS ,
Table: IBY_BEP_ACCT_OPT_NAME_B 12.1.1
owner:IBY, object_type:TABLE, fnd_design_data:IBY.IBY_BEP_ACCT_OPT_NAME_B, object_name:IBY_BEP_ACCT_OPT_NAME_B, status:VALID, product: IBY - Payments , implementation_dba_data: IBY.IBY_BEP_ACCT_OPT_NAME_B ,
Table: IBY_PMT_SYS_FORMATS 12.1.1
owner:IBY, object_type:TABLE, fnd_design_data:IBY.IBY_PMT_SYS_FORMATS, object_name:IBY_PMT_SYS_FORMATS, status:VALID, product: IBY - Payments , implementation_dba_data: IBY.IBY_PMT_SYS_FORMATS ,
Table: 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, product: IBY - Payments , implementation_dba_data: IBY.IBY_PAY_INSTRUCTIONS_H ,
Table: IBY_PMTSCHEMES 12.1.1
owner:IBY, object_type:TABLE, fnd_design_data:IBY.IBY_PMTSCHEMES, object_name:IBY_PMTSCHEMES, status:VALID, product: IBY - Payments , description: IBY_PMTSCHEMES contains a list of Payment Schemes that will be supported by a BEP , implementation_dba_data: IBY.IBY_PMTSCHEMES ,
Table: IBY_BEP_ACCT_OPT_NAME_B 12.2.2
owner:IBY, object_type:TABLE, fnd_design_data:IBY.IBY_BEP_ACCT_OPT_NAME_B, object_name:IBY_BEP_ACCT_OPT_NAME_B, status:VALID, product: IBY - Payments , implementation_dba_data: IBY.IBY_BEP_ACCT_OPT_NAME_B ,
Table: IBY_BEPLANGS 12.1.1
owner:IBY, object_type:TABLE, fnd_design_data:IBY.IBY_BEPLANGS, object_name:IBY_BEPLANGS, status:VALID, product: IBY - Payments , description: IBY_BEPLANGS contains list of all the languages supported by the Back End Payment System , implementation_dba_data: IBY.IBY_BEPLANGS ,
Table: IBY_PMTSCHEMES 12.2.2
owner:IBY, object_type:TABLE, fnd_design_data:IBY.IBY_PMTSCHEMES, object_name:IBY_PMTSCHEMES, status:VALID, product: IBY - Payments , description: IBY_PMTSCHEMES stores a list of payment schemes that are supported by a payment system. , implementation_dba_data: IBY.IBY_PMTSCHEMES ,
Table: IBY_BEPLANGS 12.2.2
owner:IBY, object_type:TABLE, fnd_design_data:IBY.IBY_BEPLANGS, object_name:IBY_BEPLANGS, status:VALID, product: IBY - Payments , description: IBY_BEPLANGS contains list of all the languages supported by the Back End Payment System , implementation_dba_data: IBY.IBY_BEPLANGS ,
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_FNDCPT_SYS_DC_PF_B 12.1.1
owner:IBY, object_type:TABLE, fnd_design_data:IBY.IBY_FNDCPT_SYS_DC_PF_B, object_name:IBY_FNDCPT_SYS_DC_PF_B, status:VALID, product: IBY - Payments , implementation_dba_data: IBY.IBY_FNDCPT_SYS_DC_PF_B ,
Table: IBY_PMT_SYS_FORMATS 12.2.2
owner:IBY, object_type:TABLE, fnd_design_data:IBY.IBY_PMT_SYS_FORMATS, object_name:IBY_PMT_SYS_FORMATS, status:VALID, product: IBY - Payments , implementation_dba_data: IBY.IBY_PMT_SYS_FORMATS ,
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_FNDCPT_SYS_EFT_PF_B 12.1.1
owner:IBY, object_type:TABLE, fnd_design_data:IBY.IBY_FNDCPT_SYS_EFT_PF_B, object_name:IBY_FNDCPT_SYS_EFT_PF_B, status:VALID, product: IBY - Payments , implementation_dba_data: IBY.IBY_FNDCPT_SYS_EFT_PF_B ,
Table: IBY_FNDCPT_SYS_DC_PF_B 12.2.2
owner:IBY, object_type:TABLE, fnd_design_data:IBY.IBY_FNDCPT_SYS_DC_PF_B, object_name:IBY_FNDCPT_SYS_DC_PF_B, status:VALID, product: IBY - Payments , implementation_dba_data: IBY.IBY_FNDCPT_SYS_DC_PF_B ,
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_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 ,
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_SYS_PMT_PROFILES_B 12.1.1
owner:IBY, object_type:TABLE, fnd_design_data:IBY.IBY_SYS_PMT_PROFILES_B, object_name:IBY_SYS_PMT_PROFILES_B, status:VALID, product: IBY - Payments , implementation_dba_data: IBY.IBY_SYS_PMT_PROFILES_B ,
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_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, product: IBY - Payments , description: IBY_PAY_INSTRUCTIONS_H stores historical snapshots of payment instructions. This table contains denormalized versions of payment instructions from specific points in time, including when the payment instruction was submitted to a payment sy , implementation_dba_data: IBY.IBY_PAY_INSTRUCTIONS_H ,
Table: IBY_FNDCPT_SYS_EFT_PF_B 12.2.2
owner:IBY, object_type:TABLE, fnd_design_data:IBY.IBY_FNDCPT_SYS_EFT_PF_B, object_name:IBY_FNDCPT_SYS_EFT_PF_B, status:VALID, product: IBY - Payments , implementation_dba_data: IBY.IBY_FNDCPT_SYS_EFT_PF_B ,
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_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 ,
Table: IBY_SYS_PMT_PROFILES_B 12.2.2
owner:IBY, object_type:TABLE, fnd_design_data:IBY.IBY_SYS_PMT_PROFILES_B, object_name:IBY_SYS_PMT_PROFILES_B, status:VALID, product: IBY - Payments , description: "This table stores Payment Process Profile setup for Funds Disbursement transactions. This table also stores information of the seeded Payment process profiles. IBY_SYS_PMT_PROFILES_B stores information that specifies the bulk of payment , implementation_dba_data: IBY.IBY_SYS_PMT_PROFILES_B ,
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 ,
View: IBY_F_LENDER_CONTACTS_V 12.2.2
owner:APPS, object_type:VIEW, fnd_design_data:IBY.IBY_F_LENDER_CONTACTS_V, object_name:IBY_F_LENDER_CONTACTS_V, status:VALID, product: IBY - Payments , implementation_dba_data: APPS.IBY_F_LENDER_CONTACTS_V ,
View: IBY_F_LENDER_CONTACTS_V 12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:IBY.IBY_F_LENDER_CONTACTS_V, object_name:IBY_F_LENDER_CONTACTS_V, status:VALID, product: IBY - Payments , implementation_dba_data: APPS.IBY_F_LENDER_CONTACTS_V ,
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 ,
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 ,
View: IBY_F_T_CRDT_APPS_V 12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:IBY.IBY_F_T_CRDT_APPS_V, object_name:IBY_F_T_CRDT_APPS_V, status:VALID, product: IBY - Payments , implementation_dba_data: APPS.IBY_F_T_CRDT_APPS_V ,
View: IBY_F_T_CRDT_APPS_V 12.2.2
owner:APPS, object_type:VIEW, fnd_design_data:IBY.IBY_F_T_CRDT_APPS_V, object_name:IBY_F_T_CRDT_APPS_V, status:VALID, product: IBY - Payments , implementation_dba_data: APPS.IBY_F_T_CRDT_APPS_V ,