Results for “iby_payment_methods_b”

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

Overview

IBY.IBY_PAYMENT_METHODS_B is the core definition table for payment methods supported by Oracle Payments (IBY) in Oracle E-Business Suite 12.1.1 and 12.2.2. A payment method is a payment attribute on a document payable that indicates how the first party payer will make the payment — for example, check, electronic funds transfer, wire, or clearing. The _B suffix designates the base (non-translated) table, holding language-independent attributes; when a 12.2.2 editioned configuration is in place, the ZD_EDITION_NAME column participates with PAYMENT_METHOD_CODE in the unique business key. Translated descriptive text is stored in the companion IBY_PAYMENT_METHODS_TL table.

From a dimensional modeling perspective, the mined foreign-key structure classifies this object as hub-leaning: it holds a stable, uniquely identified business concept (PAYMENT_METHOD_CODE) that numerous transactional and configuration tables reference. This makes it a natural hub candidate in a Data Vault model, with the many referencing tables acting as links or satellites.

Key Information Stored

The table contains 44 documented columns. The most significant are summarized below.

• PAYMENT_METHOD_CODE — the primary key (IBY_PAYMENT_METHODS_B_PK) and business identifier for each supported payment method.
• ZD_EDITION_NAME — editioning column; together with PAYMENT_METHOD_CODE it forms the unique index IBY_PAYMENT_METHODS_B_U1 in 12.2.2.
• SEEDED_FLAG — indicates whether the row was delivered as seeded Oracle data versus user-defined.
• SUPPORT_BILLS_PAYABLE_FLAG — signals whether the method is valid for Oracle Payables documents.
• DOCUMENT_CATEGORY_CODE — associates the method with a document category.
• MATURITY_DATE_OFFSET_DAYS — default offset used to derive a payment maturity date.
• ANTICIPATED_FLOAT — expected float value associated with the method.
• INACTIVE_DATE — the date the method becomes inactive.
• Applicability flags controlling attribute behavior: BANK_CHARGE_BEARER_APL_FLAG, PAYMENT_REASON_APL_FLAG, REMITTANCE_MESSAGE1_APL_FLAG (through 3), URI_CHECK_DIGIT_APL_FLAG, DELIVERY_CHANNEL_APL_FLAG, PAYMENT_FORMAT_APL_FLAG, SETTLEMENT_PRIORITY_APL_FLAG, EXCLUSIVE_PMT_APL_FLAG, and EXTERNAL_BANK_ACCT_APL_FLAG.
• FORMAT_VALUE — payment format reference value used during formatting.
• Standard audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, OBJECT_VERSION_NUMBER — plus the ATTRIBUTE1 through ATTRIBUTE15 descriptive flexfield columns.

Common Use Cases and Queries

The table is most often queried to enumerate or filter the available payment methods for a payables document, payer, or payment process. A typical lookup joins the base table to its translation table to retrieve a user-visible description:

• Validation: confirm that a PAYMENT_METHOD_CODE supplied on a document payable exists and is active (INACTIVE_DATE IS NULL OR INACTIVE_DATE > SYSDATE).
• Configuration reporting: list seeded versus user-defined methods via SEEDED_FLAG, and audit which optional attributes each method enables through the *_APL_FLAG columns.
• Joining to transaction data: aggregate IBY_DOCS_PAYABLE_ALL or IBY_PAYMENTS_ALL by PAYMENT_METHOD_CODE to report payment volumes and settlement behavior by method.
• Extensibility: report on the ATTRIBUTE1..15 and FORMAT_VALUE columns where custom configurations or format mappings have been applied.

Related Objects

The table is a widely referenced hub. The most significant dependent objects, joined on PAYMENT_METHOD_CODE, are:

• IBY_PAYMENT_METHODS_TL — translated names and descriptions (composite with PAYMENT_METHOD_CODE).
• IBY_DOCS_PAYABLE_ALL and IBY_DOCUMENTS_PAYABLE_H — documents payable carrying the payment method.
• IBY_PAYMENTS_ALL — actual payment records.
• IBY_PAYMENT_RULES — rules associated with a payment method.
• IBY_APPLICABLE_PMT_MTHDS — mapping of which methods apply to a given payer or payment profile.
• IBY_EXT_PARTY_PMT_MTHDS — payment methods linked to external parties.
• IBY_EXTERNAL_PAYEES_ALL and IBY_TEMP_EXT_PAYEES — via DEFAULT_PAYMENT_METHOD_CODE.
• IBY_VAL_ASSIGNMENTS — validation assignments referencing the method.

These relationships confirm the object's role as the central reference point for payment method metadata throughout Oracle Payments.