Search Results last_used_number_1




Overview

IBY_ACCT_PMT_PROFILES_B is a core 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 stores account-level payment profile information that completes the specification of how payment instructions are handled for a given payment profile. Entries in this table are derived from, and layered on top of, entries in the system-level IBY_SYS_PMT_PROFILES table; the combination of the system profile and the account profile determines the effective processing behavior used during payment instruction creation and formatting.

The table is owned by the IBY schema and is classified as VALID. Because payment profiles are an optional, additive refinement keyed to a single owning entity, the heuristic Data Vault classification of this table is satellite-leaning. In a Data Vault model this would suggest treating the profile as a satellite attached to its business key rather than an independent hub or a link between equal-weight entities.

Key Information Stored

The table contains 24 documented columns, of which the primary-key and business-critical attributes are the most significant:

Common Use Cases and Queries

Typical scenarios include validating which payment profiles are still active, reconciling profile usage against payments and instructions, and reporting on numbering sequences. Because the translation table IBY_ACCT_PMT_PROFILES_TL references this table on PAYMENT_PROFILE_ID, name lookups should join the two.

Joining the profile to its system template:

  • SELECT p.PAYMENT_PROFILE_ID, p.SYSTEM_PROFILE_CODE, p.TRANSMIT_CONFIGURATION_ID
    FROM IBY.IBY_ACCT_PMT_PROFILES_B p
    JOIN IBY.IBY_SYS_PMT_PROFILES_B s ON p.SYSTEM_PROFILE_CODE = s.SYSTEM_PROFILE_CODE;

Finding orphaned or inactive profiles:

  • SELECT PAYMENT_PROFILE_ID, INACTIVE_DATE
    FROM IBY.IBY_ACCT_PMT_PROFILES_B
    WHERE INACTIVE_DATE IS NOT NULL;

Reporting profile usage in payment processing requires joining IBY_PAYMENTS_ALL and IBY_PAY_INSTRUCTIONS_ALL on PAYMENT_PROFILE_ID. Edition-aware queries should include ZD_EDITION_NAME to avoid duplicate edition rows.

Related Objects

  • IBY_SYS_PMT_PROFILES_B — parent system-level profile, joined on SYSTEM_PROFILE_CODE.
  • IBY_BEPKEYS — payment system account, joined on BEP_ACCOUNT_ID.
  • IBY_TRANSMIT_CONFIGS_B — transmission settings, joined on TRANSMIT_CONFIGURATION_ID.
  • IBY_ACCT_PMT_PROFILES_TL — translation table, joined on PAYMENT_PROFILE_ID for profile names.
  • IBY_PAYMENTS_ALL, IBY_PAY_INSTRUCTIONS_ALL, IBY_DOCS_PAYABLE_ALL — transactional consumers referencing PAYMENT_PROFILE_ID.
  • AP_CHECKS_ALL and AP_PAYMENT_TEMPLATES — Payables-side references on PAYMENT_PROFILE_ID.