Search Results iby_pmt_sys_formats




Overview
Explore in AI Chat

Overview

The IBY_PMT_SYS_FORMATS table is a core reference table within the Oracle Payments (IBY) module of Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2. It functions as a junction or association table, defining the valid relationships between payment systems and the payment formats they support. A payment system represents a specific banking arrangement or channel (e.g., a bank or a payment network), while a payment format defines the technical structure of the payment file (e.g., BACS, NACHA, SEPA). This table is essential for ensuring that during payment process request submission, only compatible format and system combinations are available for selection, thereby enforcing business rules and technical constraints within the payment execution framework.

Key Information Stored

The table's structure is defined by its two primary key columns, which together form a unique constraint (IBY_PMT_SYS_FORMATS_PK). The data stored is purely referential, linking identifiers from other master tables.

  • PAYMENT_SYSTEM_ID: A foreign key column referencing IBY_BEPINFO.BEPID. This identifies a specific Banking Entity Participant, which is a payment system or bank configured within Oracle Payments.
  • PAYMENT_FORMAT_CODE: A foreign key column referencing IBY_FORMATS_B.FORMAT_CODE. This identifies a specific payment format, such as a country-specific electronic funds transfer (EFT) standard, that has been defined in the system.

The presence of a record in this table signifies that the payment format (PAYMENT_FORMAT_CODE) is a valid and usable option for the specified payment system (PAYMENT_SYSTEM_ID).

Common Use Cases and Queries

The primary use case is validation and list of values (LOV) population during payment process setup and submission. For instance, when a user selects a specific payment system for a payment process request, the application queries this table to determine which payment formats can be selected in the interface. Administrators also query this table to audit or manage the configuration of available payment methods.

A typical diagnostic or reporting query would join to the related descriptive tables:

SELECT b.bep_name, f.format_name
FROM iby.iby_pmt_sys_formats psf,
     iby.iby_bepinfo b,
     iby.iby_formats_b f
WHERE psf.payment_system_id = b.bepid
  AND psf.payment_format_code = f.format_code
ORDER BY b.bep_name;

This query returns a readable list of all configured payment systems and the formats each one supports.

Related Objects

As indicated by the foreign key constraints, IBY_PMT_SYS_FORMATS sits at the intersection of two major payment master tables.

  • IBY_BEPINFO: The master table for Banking Entity Participant (payment system) definitions. The PAYMENT_SYSTEM_ID column references IBY_BEPINFO.BEPID.
  • IBY_FORMATS_B: The base table for payment format definitions. The PAYMENT_FORMAT_CODE column references IBY_FORMATS_B.FORMAT_CODE.

This table is primarily referenced by the Oracle Payments application logic and public APIs that govern payment process submission and validation. It is a critical component in the data model that links the "how" (format) with the "where" (system) for electronic payments.