Search Results iby_pmtschemes_uk

Overview

The IBY_PMTSCHEMES table is a core reference table within the Oracle Payments (IBY) module of Oracle E-Business Suite (EBS) versions 12.1.1 and 12.2.2. It functions as a master repository for defining and managing the specific payment schemes that are supported by configured payment systems. A payment scheme represents a standardized method or protocol for transferring funds, such as BACS, SEPA Credit Transfer, SWIFT, or a proprietary electronic funds transfer (EFT) format. The table's primary role is to establish the valid relationships between a Business Event Processor (BEP), which represents a payment system, and the specific transaction formats it can process, thereby enabling the correct routing and formatting of outbound payment instructions.

Key Information Stored

The table's structure is designed to map payment schemes to their supporting systems. Its primary key is a composite of two columns, ensuring a unique combination for each supported scheme per processor. The critical columns include:

• BEPID: A foreign key column referencing IBY_BEPINFO.BEPID. This identifies the specific payment system or Business Event Processor.
• PMTSCHEMEID: A unique identifier for the payment scheme itself (e.g., SCT for SEPA Credit Transfer). This column, combined with BEPID, forms the primary key (IBY_PMTSCHEMES_UK).
• Additional descriptive columns, which may include the scheme's name, a functional code, and status indicators, further characterize each payment method, though the provided metadata does not list them explicitly.

Common Use Cases and Queries

This table is central to payment setup and validation. A common use case is during the configuration of a payment process profile, where an administrator must select which payment methods are available for a given payment system. The data in IBY_PMTSCHEMES provides the valid list of options. For troubleshooting and reporting, queries often join this table to IBY_BEPINFO to list all supported schemes per processor or to validate if a specific scheme is enabled. A typical analytical query might be:

SELECT b.bep_code, p.pmtschemeid
FROM iby_bepinfo b, iby_pmtschemes p
WHERE b.bepid = p.bepid
ORDER BY b.bep_code;

This data is also critical for the payment formatting engine, which consults this mapping to select the correct formatting template (e.g., XML, flat file) for a given payment instruction based on its assigned scheme and processor.

Related Objects

IBY_PMTSCHEMES has direct relationships with several other key Payments tables, forming the backbone of the payment processing setup.

• IBY_BEPINFO: This is the primary parent table, as defined by the foreign key constraint. IBY_BEPINFO stores the master definition of the payment system (BEP), and IBY_PMTSCHEMES defines which schemes each one supports.
• IBY_PMTSCHEMES_TL (Typical EBS pattern): A seeded translation table likely exists to store the user-facing name of the payment scheme in multiple languages.
• Payment Process Profiles: Configuration entities within the Oracle Payments Manager (OPM) user interface reference the valid BEP and Scheme combinations stored here.
• Various formatting and validation engine APIs within the IBY module internally reference this table to enforce business rules during payment instruction creation and file generation.