Search Results outbound_pmt_file_prefix




Overview
Explore in AI Chat

Overview

IBY_SYS_PMT_PROFILES_B is the foundational setup table in the Oracle Payments (IBY) module that stores Payment Process Profile definitions for Funds Disbursement transactions. A Payment Process Profile governs how Oracle EBS builds, formats, transmits, and confirms payments across a payment instruction lifecycle. This table stores both user-defined profiles created during implementation and the seeded payment process profiles delivered by Oracle, which explains the prominent SEEDED_FLAG column.

The table is owned by the IBY schema and resides in the 12.1.1 and 12.2.2 releases with a documented physical schema of 69 columns. Its primary key is IBY_SYS_PMT_PROFILES_B_PK, defined on SYSTEM_PROFILE_CODE, and a secondary unique index (IBY_SYS_PMT_PROFILES_B_U1) exists on SYSTEM_PROFILE_CODE and ZD_EDITION_NAME, which indicates the table participates in the Edition-Based Redefinition (EBR) model introduced in 12.2. The primary key is the surrogate identifier: SYSTEM_PROFILE_CODE is a system-generated, immutable key rather than a user-visible business name.

Based on the foreign key topology—many other configuration tables reference this table by SYSTEM_PROFILE_CODE—the metadata suggests a satellite-leaning Data Vault classification for this central configuration hub.

Key Information Stored

The following columns are the most significant for understanding and querying a Payment Process Profile:

The multilanguage text name and description for the profile reside in IBY_SYS_PMT_PROFILES_TL, joined by SYSTEM_PROFILE_CODE.

Common Use Cases and Queries

Consultants and DBAs commonly query this table to inventory the Payment Process Profiles configured in an environment, to determine which profile drives a specific payment format, or to troubleshoot payment file generation. A representative query to list active profiles with their format and bank entry point follows:

  • SELECT p.SYSTEM_PROFILE_CODE, t.USER_PROFILE_NAME, p.PROCESSING_TYPE, p.SEEDED_FLAG, p.INACTIVE_DATE FROM IBY_SYS_PMT_PROFILES_B p JOIN IBY_SYS_PMT_PROFILES_TL t ON t.SYSTEM_PROFILE_CODE = p.SYSTEM_PROFILE_CODE WHERE t.LANGUAGE = USERENV('LANG');

Additional patterns include identifying all profiles that use a particular payment format (WHERE PAYMENT_FORMAT_CODE = :format), isolating seeded versus custom profiles (WHERE SEEDED_FLAG = 'N'), and joining to IBY_ACCT_PMT_PROFILES_B via SYSTEM_PROFILE_CODE to map system profiles to account-level profiles used in a funds disbursement instruction. Reporting on profile-to-format and profile-to-protocol combinations is also common during upgrade impact analysis between 12.1.1 and 12.2.2.

Related Objects

  • IBY_ACCT_PMT_PROFILES_B — References this table via SYSTEM_PROFILE_CODE; holds the account-level payment profiles.
  • IBY_APPLICABLE_PMT_PROFS — References SYSTEM_PROFILE_CODE; defines which profiles apply to given payment scenarios.
  • IBY_REMIT_ADVICE_SETUP — References SYSTEM_PROFILE_CODE; controls remittance advice generation.
  • IBY_PMT_CREATION_RULES and IBY_INSTR_CREATION_RULES — Reference SYSTEM_PROFILE_CODE to define how payments and instructions are grouped and created.
  • IBY_PMT_LOGICAL_GRP_RULES — References SYSTEM_PROFILE_CODE; governs logical grouping of payments.
  • IBY_SYS_PMT_PROFILES_TL — Multilanguage translation table joined on SYSTEM_PROFILE_CODE.
  • IBY_BEPINFO — Parent of BEPID; defines the payment system/entry point.
  • IBY_FORMATS_B — Referenced by the three format columns for payment, positive pay, and letter formats.
  • IBY_TRANSMIT_PROTOCOLS_B, IBY_BANK_INSTRUCTIONS_B — Referenced by TRANSMIT_PROTOCOL_CODE and BANK_INSTRUCTIONn_CODE respectively.