Results for “iby_external_payees_all_s”

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

Overview

The APPS.IBY_SUPP_BANK_MERGE_PUB package body implements the public PL/SQL API used within Oracle Payments (IBY) to consolidate supplier and external payee bank account information when duplicate trading partners are merged. During supplier merge operations driven from Oracle Payables or Oracle Procurement, party and payee records held in the TCA (Trading Community Architecture) and Payments schemas must be repointed so that payment instruments, payment instruction uses, and account ownership rows continue to reference the surviving supplier or payee. This package provides the mechanism that performs that repointing for bank account–related data.

The object resides in the APPS schema, holds VALID status, and is classified as a PUB (public) API, indicating it is designed for supported invocation by other Oracle EBS modules and, where documented, by customer extensions. The body is not referenced by any other database object, confirming it acts as a stand-alone entry point rather than an internal utility consumed elsewhere in the schema.

Key Procedures and Functions

ETRM documents a single public procedure for this package body: BANK_ACCOUNTS_MERGE. This procedure encapsulates the bank account merge logic. Its role is to reassign the bank account records associated with a source supplier site or external payee to the designated target, ensuring that payment instruments and their usage records remain valid and correctly attributed after the merge. The procedure relies on the standard Oracle Application Object Library error-handling stack, including FND_API, FND_MSG_PUB, and FND_MESSAGE, so that completion status and any validation failures can be reported to the calling process through the conventional API return and message conventions. Logging is performed through FND_LOG, and informational output can be directed to the concurrent manager log via FND_FILE.

No parameter list is documented in the ETRM metadata for BANK_ACCOUNTS_MERGE. Consumers should consult the package specification in the target environment to obtain the exact signature before invocation.

Tables Accessed

The package body references several base tables through APPS synonyms:

• AP_SUPPLIER_SITES_ALL — supplier site information used to identify the source and target of the merge.
• IBY_PMT_INSTR_USES_ALL and IBY_PMT_INSTR_USES_ALL_S — the payment instrument usage records (the table most commonly associated with the search term iby_pmt_instr_uses_all_s) that map payment instruments to a supplier site, payee, or account owner; these are updated to point to the surviving entity.
• IBY_EXTERNAL_PAYEES_ALL and IBY_EXTERNAL_PAYEES_ALL_S — external payee definitions affected by the merge.
• IBY_ACCOUNT_OWNERS and IBY_ACCOUNT_OWNERS_S — account owner records that link bank accounts to payees or suppliers, which must be reassigned.
• DUAL and PLITBLM — supporting references for PL/SQL constructs and helper calls.

The inclusion of the _S (sequence/interface) variants alongside the base tables reflects Oracle Payments' pattern of maintaining both transactional and surrogate keyed records for payment instrument usage and external payees.

Usage Notes

IBY_SUPP_BANK_MERGE_PUB.BANK_ACCOUNTS_MERGE is typically invoked from the supplier merge concurrent program or from the supplier merge form flow in Oracle Payables, where the Oracle Payments layer must reconcile bank account ownership as part of the overall supplier consolidation. It may also be called from custom code during data migration or de-duplication projects, provided the caller observes the standard FND API success/failure conventions.

The package depends on IBY_DISBURSEMENT_SETUP_PUB and HZ_UTILITY_PUB, indicating that disbursement setup validation and TCA utility routines are consulted during processing. Because it is a PUB API, Oracle supports its use at documented integration points, but direct updates to the underlying IBY_PMT_INSTR_USES_ALL tables should be avoided in favour of this API to preserve data integrity.