Search Results iby_applicable_pmt_profs_pk

Overview

The IBY_APPLICABLE_PMT_PROFS table is a core data object within the Oracle Payments (IBY) module of Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2. It functions as a mapping or assignment table, defining the relationships between system payment profiles and the specific business entities or contexts where those profiles are valid for use. A system payment profile (IBY_SYS_PMT_PROFILES_B) contains the detailed configuration for processing electronic payments, such as bank details, file formats, and transmission protocols. This table's primary role is to control and restrict which of these configured profiles can be applied to different payment processes, ensuring the correct banking and processing rules are invoked based on the transaction's context, such as a specific operating unit, legal entity, or payment document.

Key Information Stored

The table's structure is designed to store assignment records. Its primary key, APPLICABLE_PMT_PROF_ID, uniquely identifies each assignment rule. The most critical column is SYSTEM_PROFILE_CODE, a foreign key that references the IBY_SYS_PMT_PROFILES_B table to identify the specific payment profile being assigned. While the provided ETRM metadata does not list all columns, typical columns in such an assignment table in Oracle Payments would include context-defining attributes. These often encompass identifiers like ORG_ID (Operating Unit), ORG_TYPE, PAYMENT_DOCUMENT_ID, and potentially INVOICE_CURRENCY_CODE or PAYMENT_CURRENCY_CODE. These columns define the business context to which the SYSTEM_PROFILE_CODE is linked, enabling a many-to-many relationship between profiles and applicable contexts.

Common Use Cases and Queries

A primary use case is troubleshooting payment process failures or unexpected profile selections. An administrator can query this table to verify which payment profiles are assigned to a given operating unit. Common reporting needs include listing all assignment rules or identifying unused profiles. Sample SQL patterns include joining to the profile master table for descriptive information.

• To find all profiles applicable to a specific operating unit (e.g., ORG_ID=204):
  SELECT prof.system_profile_code, prof.profile_name
FROM iby_applicable_pmt_profs app, iby_sys_pmt_profiles_b prof
WHERE app.system_profile_code = prof.system_profile_code
AND app.org_id = 204;
• To list all assignment rules with profile details:
  SELECT app.applicable_pmt_prof_id, app.system_profile_code, prof.profile_name, app.org_id
FROM iby_applicable_pmt_profs app
LEFT JOIN iby_sys_pmt_profiles_b prof ON app.system_profile_code = prof.system_profile_code;

Related Objects

The table has documented foreign key relationships with other critical Payments tables, forming the backbone of the profile assignment logic.

• IBY_SYS_PMT_PROFILES_B: This is the master table for system payment profiles. The relationship is established via the column IBY_APPLICABLE_PMT_PROFS.SYSTEM_PROFILE_CODE, which references IBY_SYS_PMT_PROFILES_B.SYSTEM_PROFILE_CODE. This join is essential for retrieving the full configuration details of the assigned profile.
• Primary Key Constraint: The table is governed by the primary key IBY_APPLICABLE_PMT_PROFS_PK on the column APPLICABLE_PMT_PROF_ID. This unique identifier is often referenced by other application logic or audit tables within the IBY schema.