Results for “outbound_replace_chars”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

IBY_BEPINFO is the master reference table for payment systems (also referred to as BEPs — Bank Entry Points or payment system connectors) within the Oracle Payments (IBY) module of Oracle E-Business Suite 12.1.1 and 12.2.2. Each row describes a single external payment system or payment gateway that Oracle Payments can communicate with, capturing its identity, connectivity details, credentials, operational capabilities, and default processing behavior. In Oracle Payments architecture, this table is the anchor point for configuring and orchestrating disbursement and fund capture flows, including EFT, ACH, wire, and card-based payment settlement channels.

From a data modeling perspective, the heuristic Data Vault classification is hub. IBY_BEPINFO represents the core business entity (the payment system), keyed by a stable surrogate identifier and referenced by a large family of dependent satellite-style tables that record keys, formats, profiles, transmission configuration, and transactional summaries.

Key Information Stored

The table is documented with 54 columns. The most functionally significant columns are:

• BEPID — the surrogate primary key (IBY_BEPINFO_PK); the unique identifier used by all referencing tables.
• NAME — the descriptive name of the payment system; a business-key candidate (IBY_BEPINFO_NAME_U2).
• SUFFIX — the short system suffix used in formatting and routing; a business-key candidate (IBY_BEPINFO_SUFFIX_U3), and the object of the user's search term iby_bep_suffix_uk.
• BASEURL, ADMINURL, LOGINURL, LOGOUTURL — endpoint URLs for service invocation and administrative access.
• BEPUSERNAME, BEPPASSWORD, PSUSERNAME, PSPASSWORD — credentials used for outbound authentication to the payment system.
• BEP_TYPE — classifies the payment system type (for example, standard versus direct capture style integrations).
• ACTIVESTATUS, INACTIVE_DATE, SEEDED_FLAG — lifecycle and Oracle-provided seed indicators.
• LEADTIME, HOLIDAYFILE, FILE_SUPPORT, MAX_BATCH_SIZE — scheduling, cutoff, and batch-processing constraints.
• PARTY_ID, BANK_ID — foreign keys to HZ_PARTIES identifying the party and bank associated with the payment system.
• OUTBOUND_INVALID_CHARS, OUTBOUND_REPLACE_CHARS — character translation rules applied to outbound payment files.
• SECURITY_GROUP_ID, ZD_EDITION_NAME, OBJECT_VERSION_NUMBER — Multi-Org security, multi-tenant edition, and concurrent-update control columns.

Common Use Cases and Queries

IBY_BEPINFO is queried primarily during payment system setup validation, disbursement troubleshooting, and reporting on payment configurations.

Locating a payment system by its suffix or name:

SELECT bepid, name, suffix, bep_type, activestatus
FROM iby_bepinfo
WHERE suffix = :p_suffix;

Listing active payment systems with their banking party:

SELECT b.bepid, b.name, b.suffix, hp.party_name
FROM iby_bepinfo b, hz_parties hp
WHERE b.party_id = hp.party_id
AND b.activestatus = 'ACTIVE';

Identifying payment systems used in disbursement batches or payment instructions involves joining through IBY_BATCHES_ALL or IBY_PAY_INSTRUCTIONS_H on the BEPID column. Configuration review typically joins IBY_PMTSCHEMES, IBY_PMT_SYS_FORMATS, and IBY_SYS_PMT_PROFILES_B to verify the formats and profiles assigned to each system.

Because SUFFIX carries a unique index, application code and concurrent programs frequently resolve an inbound file's origin by matching on SUFFIX rather than BEPID, making it a common filter in reconciliation and file-parsing logic.

Related Objects

The following relationships are the most significant for impact analysis and joins:

• IBY_PMTSCHEMES — payment schemes assigned to the payment system (BEPID).
• IBY_PMT_SYS_FORMATS — file format definitions for disbursement (PAYMENT_SYSTEM_ID).
• IBY_PMT_SYS_TRANSMISSIONS — transmission and delivery configuration (BEPID).
• IBY_BATCHES_ALL — payment batches processed through the system (BEPID).
• IBY_PAY_INSTRUCTIONS_H — payment instructions referencing the system (BEPID).
• IBY_SYS_PMT_PROFILES_B — system payment profiles (BEPID).
• IBY_FNDCPT_SYS_EFT_PF_B and IBY_FNDCPT_SYS_DC_PF_B — EFT and debit card profile mappings (PAYMENT_SYSTEM_ID).
• IBY_BEPKEYS, IBY_BEPLANGS, and IBY_ROUTINGINFO — credential/keys, localized labels, and routing rules (BEPID).
• HZ_PARTIES — parent party and bank references via PARTY_ID and BANK_ID.

Because more than a dozen tables carry foreign keys to BEPID, decommissioning or renaming a payment system requires reviewing all dependent configuration and transactional objects before making changes in a production environment.