Search Results iby_sys_pmt_profiles_b




Overview
Explore in AI Chat

Overview

The IBY_SYS_PMT_PROFILES_B table is a core setup table within the Oracle E-Business Suite Payments module (IBY). It stores the master definition for Payment Process Profiles, which are critical configuration entities that govern the end-to-end execution of Funds Disbursement (i.e., outgoing payments) transactions. These profiles act as templates, specifying the bulk of the payment processing logic, including formatting, transmission, and bank instructions. The table holds both user-defined profiles and Oracle-seeded profiles, providing a centralized repository for the rules that determine how payments are generated and communicated to financial institutions in both EBS 12.1.1 and 12.2.2.

Key Information Stored

The table's primary key is the SYSTEM_PROFILE_CODE, a unique identifier for each profile. Its most significant columns are foreign keys that link to other setup tables, defining the profile's behavior. Key columns include BEPID (linking to IBY_BEPINFO to identify the Bank Enterprise Publisher or payment system), TRANSMIT_PROTOCOL_CODE (defining the transmission method), and PAYMENT_FORMAT_CODE (specifying the payment file format, e.g., NACHA, BACS). Other crucial columns reference formats for positive pay files (POSITIVE_PAY_FORMAT_CODE) and payment advice letters (PAY_FILE_LETTER_FORMAT_CODE), as well as codes for optional bank instructions (BANK_INSTRUCTION1_CODE, BANK_INSTRUCTION2_CODE). This structure allows a single profile to encapsulate a complete payment processing rule set.

Common Use Cases and Queries

This table is central to troubleshooting payment process execution and understanding system configuration. Common scenarios include identifying which profiles are assigned to specific bank accounts or identifying the setup behind a failed payment submission. A typical diagnostic query joins the system profile to its related setup tables to view a complete profile definition. For example:

  • To list all payment process profiles with their associated payment format and transmission protocol: SELECT sp.system_profile_code, sp.profile_name, f.format_name, tp.protocol_name FROM iby_sys_pmt_profiles_b sp, iby_formats_b f, iby_transmit_protocols_b tp WHERE sp.payment_format_code = f.format_code(+) AND sp.transmit_protocol_code = tp.protocol_code(+);
  • To find profiles using a specific BEP (payment system): SELECT system_profile_code, profile_name FROM iby_sys_pmt_profiles_b WHERE bepid = (SELECT bepid FROM iby_bepinfo WHERE bep_name = '&BEP_NAME');

Reporting often involves joining to IBY_ACCT_PMT_PROFILES_B to see profile assignments to bank accounts.

Related Objects

IBY_SYS_PMT_PROFILES_B is a major hub in the Payments schema, referenced by numerous child tables that extend or utilize its configuration. Key related objects include the translation table IBY_SYS_PMT_PROFILES_TL for multilingual names and several rule and assignment tables: IBY_ACCT_PMT_PROFILES_B (assigns profiles to bank accounts), IBY_PMT_CREATION_RULES, IBY_INSTR_CREATION_RULES, and IBY_PMT_LOGICAL_GRP_RULES. It also links to setup tables for remittance advice (IBY_REMIT_ADVICE_SETUP) and defines applicability (IBY_APPLICABLE_PMT_PROFS). Its foreign key relationships to IBY_FORMATS_B, IBY_TRANSMIT_PROTOCOLS_B, IBY_BEPINFO, and IBY_BANK_INSTRUCTIONS_B are essential for retrieving the descriptive details of the referenced setup entities.