Search Results pos_sbd_iby_pkg




Overview
Explore in AI Chat

Overview

POS_SBD_IBY_PKG is a PL/SQL package owned by the APPS schema that supports Oracle Payables supplier bank account onboarding and maintenance within the Oracle iPayment (IBY) framework. Its name reflects its association with the Supplier Banking Data (SBD) functionality of Oracle Payables, which manages the registration, validation, and approval of external payee bank accounts used for electronic payment disbursements. The package acts as an intermediary layer between Payables supplier account workflows and the underlying IBY payment instrument tables, allowing supplier bank account requests to be staged, validated, approved, and ultimately assigned to supplier sites. It is a valid, active object in release 12.1.1 and 12.2.2 and is referenced by POS_SBD_PKG, indicating it forms part of a cohesive set of supplier banking utilities.

Key Procedures and Functions

The package exposes eleven documented procedures and functions covering the full lifecycle of a supplier bank account request:

Tables Accessed

The package operates across supplier, trading partner, and payment instrument data. It reads and writes supplier site information in AP_SUPPLIER_SITES_ALL and supplier mapping data in POS_SUPPLIER_MAPPINGS. Party and location data is sourced from HZ_PARTIES, HZ_PARTY_SITES, and HZ_LOCATIONS. Payment instrument and payee records are held in IBY_EXTERNAL_PAYEES_ALL, IBY_EXT_BANK_ACCOUNTS, IBY_ACCOUNT_OWNERS, and IBY_PMT_INSTR_USES_ALL. The staging and approval workflow relies on IBY_TEMP_EXT_BANK_ACCTS and its shadow table IBY_TEMP_EXT_BANK_ACCTS_S. Request tracking is performed through POS_ACNT_ADDR_SUMM_REQ and POS_ACNT_GEN_REQ. DUAL is used for singleton queries.

Usage Notes

POS_SBD_IBY_PKG is typically invoked indirectly rather than called directly by end users. It is called by POS_SBD_PKG, which in turn is surfaced through the Oracle Payables supplier bank account user interface and related self-service supplier registration flows. The procedures support the account request lifecycle: staging via CREATE_IBY_TEMP_ACCOUNT, validation via VALIDATE_ACCOUNT and CHECK_FOR_DUPLICATES, approval via APPROVE_IBY_TEMP_ACCOUNT, prenote processing via PRENOTE_IBY_TEMP_ACCOUNT, and final assignment via ASSIGN_SITE_TO_ACCOUNT. Customizations should avoid direct calls where possible and instead extend through the supported Payables and iPayment APIs, because the package references internal staging tables whose structure is subject to change between patch levels. Its dependency on STANDARD and the APPS synonym layer confirms it is intended for execution within the standard Oracle EBS runtime environment.