Search Results iby_bepinfo_pk

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.