Search Results iby_internal_payers_all




Overview
Explore in AI Chat

Overview

IBY_INTERNAL_PAYERS_ALL is a Payments (IBY) module table that stores the payment-processing attributes controlling the funds disbursement payment flow for all first-party payers. In Oracle EBS 12.1.1 and 12.2.2, a first-party payer is the internal organization (or business unit) that disburses funds on behalf of the enterprise — for example, a paying legal entity or operating unit. Each row represents one internal payer and defines behavioral rules that determine how Oracle Payments builds, reviews, formats, and submits payment instructions. Because these attributes directly govern the payment process, misconfigured rows can block payment instruction creation, alter payment rejection behavior, or change how payment files are retained.

The documented Data Vault classification for this object is standalone, meaning the FK structure does not reveal a hub, link, or satellite relationship to other IBY entities. From a modeling perspective, this suggests treating IBY_INTERNAL_PAYERS_ALL as an independent reference (master) table keyed on the internal payer, rather than a transactional child of a payments hub. The single-row-per-payer nature and the presence of audit columns (CREATED_BY, LAST_UPDATE_DATE) are consistent with a configuration/reference entity rather than an event table.

Key Information Stored

The table contains 20 documented columns. The most significant include:

The documented unique index IBY_INTERNAL_PAYERS_ALL_U1 (INT_PAYER_ID, ZD_EDITION_NAME) is the business-key candidate, while INT_PAYER_ID alone is the surrogate primary key.

Common Use Cases and Queries

A frequent requirement is auditing payer-level payment controls. A representative query lists active payers and their key flags:

  • SELECT int_payer_id, org_id, org_type, payment_method_at_payee_flag, require_prop_pmts_review_flag, save_payment_file_in_db, zd_edition_name FROM iby.iby_internal_payers_all WHERE org_id = :p_org_id;

Configuration teams use such queries to verify that a paying business unit does not unintentionally force manual review or retain payment files in the database. Oracle Payments internally reads these rows when building payment instructions, so troubleshooting a stuck payment process often begins by inspecting the payer's flags. Reporting on the BANK_CHARGE_BEARER and PPR_REPORT_FORMAT columns supports bank-charge reconciliation and Payment Process Request report formatting.

Related Objects

Because the mined relationship data classifies IBY_INTERNAL_PAYERS_ALL as standalone, no formal foreign keys connect it to other IBY tables in the documented structure. The significant consumption of these rows is algorithmic rather than referential, occurring within the payments engine:

Joins are typically performed on ORG_ID/ORG_TYPE rather than a foreign-key column, reflecting the reference-table role of this object.