Search Results iby_accppmtmthd_pkg




Overview
Explore in AI Chat

Overview

IBY_ACCPPMTMTHD_PKG is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite, situated within the Payments (IBY) module. Its name reflects its purpose: managing account payment methods — the association between a payee, an account type, and a payment method used when disbursing funds. In Oracle Payments, a payee can hold multiple payment methods across different accounts (for example, a supplier who accepts both electronic funds transfer and check). This package encapsulates the create, validate, and delete operations governing those account-level payment method records, giving callers a controlled programmatic interface rather than direct DML against the underlying table.

The package is classified as OTHER in the ETRM metadata (not a formal public API), yet it plays a structural role: five other IBY packages depend on it, including the transaction layer packages (IBY_TRANSACTIONEFT_PKG, IBY_TRANSACTIONCC_PKG, IBY_TRANSACTIONSET_PKG), the offline database package, and the core IBY_FIPAYMENTS_PKG. This dependency pattern indicates that account payment method maintenance is a prerequisite step for payment transaction processing and for the offline payment database synchronization.

Key Procedures and Functions

  • GETMPAYEEID — Retrieves the payee identifier associated with an account payment method record. Callers use it to resolve the owning payee when only the payment method row context is available.
  • PMTMTHDEXISTS — Performs an existence check to determine whether a given payee/account/payment method combination is already defined. This guards against duplicate records before insertion.
  • CREATEACCPPMTMTHD — Inserts a new account payment method record, binding a payee to an account type and payment method. This is the primary maintenance entry point used by dependent packages and forms.
  • DELETEACCPPMTMTHD — Removes an existing account payment method record, typically invoked when a payee's payment preference is discontinued or corrected.

The metadata documents four procedures total; no parameter lists are published in the ETRM excerpt, and none should be assumed.

Tables Accessed

  • IBY_ACCPPMTMTHD — The primary table holding account payment method definitions. Read by the existence check and payee lookup; written by the create and delete routines.
  • IBY_ACCTTYPE — The account type reference table. Consulted to validate that the account type supplied is a defined, supported type.
  • IBY_PAYEE — The payee master table. Used to validate and resolve the payee that owns the payment method association.

Access is through APPS synonyms, consistent with standard EBS schema design.

Usage Notes

IBY_ACCPPMTMTHD_PKG is invoked from three principal contexts. First, the Oracle Payments setup and payee maintenance forms, which allow users to define and remove account payment methods for suppliers and other payees. Second, dependent IBY packages: IBY_TRANSACTIONEFT_PKG and IBY_TRANSACTIONCC_PKG consult account payment method data while building EFT and credit card payment transactions, and IBY_OFFLINEDB_PKG uses it during offline payment database operations. Third, custom extensions and concurrent programs that provision payee payment methods in bulk during data conversion or interface loads.

Because the package is classified as OTHER rather than a documented public API, it should be treated as internal to Payments. Custom code that calls it directly must account for the possibility of signature changes during patching or upgrades between 12.1.1 and 12.2.2. Where feasible, developers should prefer inserting through supported public APIs or the standard setup forms, and use IBY_ACCPPMTMTHD_PKG calls only where the dependent IBY packages already establish the calling pattern.