Results for “payment_format_code”

50+ results




Overview
Explore in AI Chat

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

Overview

The IBY.IBY_PMT_SYS_FORMATS table is a foundational configuration table in the Oracle Payments (IBY) module of Oracle E-Business Suite, present in both release 12.1.1 and 12.2.2. It defines the valid association between a payment system and one or more payment formats, effectively acting as the intersection that binds a given payment system (such as a bank or clearinghouse configuration) to the specific file formats it supports. Because Oracle Payments processing depends on knowing which format template to apply for a given disbursement or funds capture path, this table governs the runtime selection of format templates during payment instruction creation and file generation.

Under the heuristic Data Vault classification mined from its foreign key structure, this object is best modeled as a link table. It resolves a many-to-many relationship between payment systems and payment formats and carries only descriptive and audit attributes — no natural business measures — which is consistent with a link construct positioned between two hubs.

Key Information Stored

The table contains ten documented columns. The most significant are the composite key and audit columns:

The surrogate primary key is IBY_PMT_SYS_FORMATS_PK, defined on (PAYMENT_SYSTEM_ID, PAYMENT_FORMAT_CODE). A separate unique index, IBY_PMT_SYS_FORMATS_ID_CODE_U1, defined on (PAYMENT_FORMAT_CODE, PAYMENT_SYSTEM_ID, ZD_EDITION_NAME), functions as the business-key candidate, enforcing uniqueness of the system-format pairing per edition.

Common Use Cases and Queries

Typical uses include reporting which formats are enabled for a payment system, validating configuration ahead of payment runs, and diagnosing format-selection failures. A representative query joins both foreign key targets:

  • Enabled formats per system: SELECT psf.PAYMENT_SYSTEM_ID, f.FORMAT_NAME FROM IBY_PMT_SYS_FORMATS psf JOIN IBY_FORMATS_B f ON f.PAYMENT_FORMAT_CODE = psf.PAYMENT_FORMAT_CODE WHERE psf.INACTIVE_DATE IS NULL;
  • System detail lookup: join IBY_BEPINFO on PAYMENT_SYSTEM_ID to resolve the system name for each association.
  • Audit reporting: filter on LAST_UPDATE_DATE to track recently modified configurations.
  • Exception troubleshooting: identify formats referenced by a payment process profile that are not present for the intended payment system.

Related Objects

The following objects are the most significant in relation to this table, based on documented foreign key and key relationships:

  • IBY_BEPINFO — joined on PAYMENT_SYSTEM_ID; the parent payment system (bank/clearinghouse) definition.
  • IBY_FORMATS_B — joined on PAYMENT_FORMAT_CODE; the base format definition table.
  • IBY_FORMATS_TL — translated format names referenced through the format code.
  • IBY_PMT_SYS_FORMATS_PK — the primary key constraint enforced on the composite columns.
  • IBY_PMT_SYS_FORMATS_ID_CODE_U1 — the unique business-key index including the edition column.
  • IBY_PAYMENT_SYSTEMS and IBY_PAY_PROCESS_PROFILES — associated configuration objects that consume system-format mappings at runtime.

Together, these relationships place IBY_PMT_SYS_FORMATS at the center of payment format resolution within Oracle Payments.