Search Results pos_acnt_pay_pref_s

Overview

APPS.POS_SBD_PKG is a supplier banking data (SBD) package body within the Oracle E-Business Suite Purchasing module, whose primary purpose is to orchestrate the creation, maintenance, approval, and removal of supplier bank account information and its associated payment preferences. In Oracle EBS 12.1.1 and 12.2.2, supplier banking records are dispersed across the supplier model (AP_SUPPLIERS), the trading community model (HZ_PARTIES, HZ_PARTY_SITES), and the Payments module's instrument tables (IBY_EXTERNAL_PAYEES_ALL, IBY_EXT_BANK_ACCOUNTS, IBY_PMT_INSTR_USES_ALL, IBY_TEMP_EXT_BANK_ACCTS). POS_SBD_PKG acts as the business-logic layer that bridges these schemas and drives them through the Payments APIs, including IBY_FNDCPT_SETUP_PUB, IBY_FNDCPT_COMMON_PUB, IBY_DISBURSEMENT_SETUP_PUB, and the internal POS_SBD_IBY_PKG and POS_SBD_TBL_PKG packages. It also integrates with Oracle Workflow (WF_ITEMS, POS_SPM_WF_PKG1) for the supplier and buyer approval lifecycle, and with FND_API, FND_GLOBAL, and FND_LOG for the standard API error-handling and logging framework. The package is classified as OTHER and is documented with sixteen procedures/functions. It is referenced by one other database object, indicating it is a foundational rather than a leaf-level package. Users searching the term "pos_acnt_pay_pref_s" encounter this package because it operates directly on the POS_ACNT_PAY_PREF and POS_ACNT_PAY_PREF_S tables that store supplier account payment preferences.

Key Procedures and Functions

The documented procedures cover the full supplier banking data lifecycle:

• SUPPLIER_ADD_ACCOUNT — Adds a new bank account for a supplier, initiating the registration flow.
• SUPPLIER_CREATE_ACCOUNT — Creates the underlying supplier account record and its IBY instrument representation.
• SUPPLIER_UPDATE_ACCOUNT — Modifies an existing supplier bank account.
• SUPPLIER_UPDATE_ASSIGNMENT — Updates the assignment of an account to a payment purpose or business unit.
• SUPPLIER_RESET_ASSIGNMENT — Resets an existing assignment to its initial or default state.
• SUPPLIER_REMOVE_ACCOUNT — Removes a supplier bank account from active use.
• BUYER_APPROVE_ACCOUNT — Buyer-side approval of a submitted supplier account.
• BUYER_REJECT_ACCOUNT — Buyer-side rejection of a submitted supplier account.
• BUYER_APPROVE_ASSIGNMENT — Buyer approval of an account-to-purpose assignment.
• BUYER_REJECT_ASSIGNMENT — Buyer rejection of an account assignment.
• BUYER_PRENOTE_ACCOUNT — Handles the prenote (prenotification) step for a buyer-approved account.
• UPDATE_PAYMENT_PREF — Maintains payment preference data, directly related to POS_ACNT_PAY_PREF and POS_ACNT_PAY_PREF_S.
• BUYER_REMOVE_ACCOUNT and REMOVE_ACCOUNT — Removal operations performed in the buyer and generic contexts respectively.
• SBD_HANDLE_ADDRESS_APV — Supports address approval handling tied to the supplier account.
• CHECKDUPSUPBANKACCT — Validates whether a supplier bank account is a duplicate before it is created or approved.

Tables Accessed

The package reads and writes several EBS tables via APPS synonyms. Supplier identity is resolved through AP_SUPPLIERS and the party model tables HZ_PARTIES and HZ_PARTY_SITES. Banking instruments are persisted in IBY_EXT_BANK_ACCOUNTS, IBY_TEMP_EXT_BANK_ACCTS, IBY_EXTERNAL_PAYEES_ALL, IBY_PMT_INSTR_USES_ALL, and IBY_ACCOUNT_OWNERS, reflecting the full instrument assignment model. The SBD-specific application tables POS_ACNT_GEN_REQ, POS_ACNT_ADDR_REQ, POS_ACNT_ADDR_SUMM_REQ, POS_ACNT_PAY_PREF, POS_ACNT_PAY_PREF_S, and POS_SUPPLIER_MAPPINGS capture account registration, address, and payment-preference requests and supplier mappings. WF_ITEMS is accessed to drive the Oracle Workflow approval items that govern buyer and supplier decisions.

Usage Notes

POS_SBD_PKG is typically invoked indirectly rather than directly. In standard EBS deployments it is called by supplier banking data user interfaces, self-service supplier registration flows, buyer approval worklists, and background workflow activities that originate in POS_SPM_WF_PKG1. Because it delegates accounting and instrument plumbing to the IBY_FNDCPT and IBY_DISBURSEMENT APIs, it is the recommended encapsulation layer for any custom code that must add, update, approve, prenote, or remove supplier bank accounts, and for any extension needing to maintain payment preference records in POS_ACNT_PAY_PREF and POS_ACNT_PAY_PREF_S. Customizations should call the public procedures rather than issuing direct DML against the underlying IBY or POS tables, thereby preserving validation, duplicate checking (CHECKDUPSUPBANKACCT), workflow integration, and the FND_LOG-based audit trail.