Search Results iby_debit_authorizations_s

Overview

IBY_FNDCPT_SETUP_PUB is a public PL/SQL package in the Oracle Payments (IBY) module that centralizes configuration and setup logic for payers, payment instruments, and payment channels within Oracle E-Business Suite 12.1.1 and 12.2.2. Its primary business purpose is to support the Funds Capture setup flow, allowing applications and forms to determine whether a payer exists, whether a payment channel is active, which instruments are assigned to a payer, and how default payment methods are configured. The package is classified as a public API (PUB) owned by APPS and is referenced by 35 other database objects, confirming its role as a foundational dependency for funds capture processing. The package constant G_DEBUG_MODULE is defined as 'iby.plsql.IBY_FNDCPT_SETUP_PUB', and the associated G_PKG_NAME constant identifies the package as 'IBY_FNDCPT_SETUP_PUB'; these are used with the FND debug/logging infrastructure to produce trace output during setup and validation operations.

Key Procedures and Functions

The package exposes 25 documented procedures and functions. They fall into several logical groupings:

• Payer attribute management: SET_PAYER_ATTRIBUTES, GET_PAYER_ATTRIBUTES, and GET_TRXN_PAYER_ATTRIBUTES manage the storage and retrieval of payer-level configuration values, including those resolved in transaction context.
• Payment channel handling: GET_PAYMENT_CHANNEL_ATTRIBS, SET_PAYER_DEFAULT_PMT_CHANNEL, GET_PAYER_DEFAULT_PMT_CHANNEL, and GET_TRXN_APPL_PMT_CHANNELS support channel validation and default resolution; Exists_Pmt_Channel verifies an active channel by code, as shown in the excerpted source.
• Instrument assignment and inquiry: SET_PAYER_INSTR_ASSIGNMENT, GET_PAYER_INSTR_ASSIGNMENTS, GET_PAYER_ALL_INSTRUMENTS, and GET_TRXN_APPL_INSTR_ASSIGN manage the mapping of payment instruments to payers and applications, while Exists_Instr validates instrument existence for credit card and bank account types.
• Credit card operations: CREATE_CARD, UPDATE_CARD, GET_CARD, CARD_EXISTS, PROCESS_CREDIT_CARD, UPDATE_CARD_WRAPPER, and CREATE_CARD_WRAPPER form the card lifecycle API surface, including wrapper routines that encapsulate validation and persistence logic.
• Utility functions: GET_PAYER_ID and GET_HASH resolve identifiers and hash values used for setup validation and referential consistency.

Tables Accessed

The package reads and writes through APPS synonyms across the IBY, HZ, and related schema objects. Core setup tables include IBY_FNDCPT_PMT_CHNNLS_B (payment channel definitions), IBY_CREDITCARD and IBY_EXT_BANK_ACCOUNTS (instrument records), IBY_EXTERNAL_PAYERS_ALL and IBY_EXTERNAL_PAYERS_ALL_S (payer registry), and IBY_PMT_INSTR_USES_ALL with its _S sequence table for instrument-to-payer assignments. Party data is sourced from HZ_PARTIES and HZ_PARTY_SITE_USES, while IBY_ACCOUNT_OWNERS, IBY_EXT_PARTY_PMT_MTHDS (and _S), IBY_PMT_MTHD_ATTRIB_APPL, and IBY_DEBIT_AUTHORIZATIONS (and _S) support payment method attributes and debit authorization state. These tables collectively provide the lookup and persistence layer required to validate setup data before a funds capture transaction is initiated.

Usage Notes

IBY_FNDCPT_SETUP_PUB is typically invoked from the Payments setup forms, funds capture concurrent programs, and dependent PL/SQL packages that require payer or instrument validation. Because it is classified as a public API, custom code should call the documented procedures rather than querying the underlying IBY tables directly. The Exists_Pmt_Channel and Exists_Instr functions are useful for lightweight validation before assignment operations, and the G_DEBUG_MODULE constant integrates with the standard FND logging framework when tracing is enabled. Callers should respect the package's validation expectations and rely on its wrapper routines when creating or updating card records.