Results for “get_le_from_bankacct_id”

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

Overview

IBY_FNDCPT_TRXN_PUB is the public PL/SQL package body that implements the transaction-level application programming interface for Oracle Payments (IBY) in Oracle E-Business Suite 12.1.1 and 12.2.2. It provides the procedural interface through which internal and external components create, retrieve, encrypt, and manage the payment transaction records that underpin funds capture processing. Transactions represent the individual authorizations, settlements, returns, and reversals generated between a payer and a payee for a given payment instrument, and this package centralizes the logic required to persist those events consistently in the IBY transaction model.

The package is classified as a PUB API in the E-Business Suite Technical Reference Manual and holds VALID status in the APPS schema. Its scope spans extension management, security code handling, and transaction event lifecycle operations, making it a foundational dependency for the broader payments architecture. Per the documented metadata, the package is referenced by 49 other packages, confirming its role as a widely reused integration point rather than a module-specific utility.

Key Procedures and Functions

The documented interface exposes 26 procedures and functions, grouped functionally as follows:

• Transaction extensions: CREATE_TRANSACTION_EXTENSION, UPDATE_TRANSACTION_EXTENSION, GET_TRANSACTION_EXTENSION, COPY_TRANSACTION_EXTENSION, and DELETE_TRANSACTION_EXTENSION manage the flexible attribute records associated with a transaction, allowing additional data to be attached to the core transaction entity.
• Security and encryption: ENCRYPT_EXTENSIONS, DECRYPT_EXTENSIONS, ENCRYPT_SECURITY_CODE, GET_SECURITY_CODE, and SECURE_WIPE_SEGMENT handle sensitive data such as card security codes and segmented account data, enforcing the encryption and secure-erasure requirements described in the security segments and subkeys model.
• Authorization and settlement events: CREATE_AUTHORIZATION, GET_AUTHORIZATION, CANCEL_AUTHORIZATION, CREATE_SETTLEMENT, CREATE_SETTLEMENTS, CREATE_RETURN, and CREATE_REVERSAL record the lifecycle events of a funds capture transaction.
• Utility functions: GET_TANGIBLE_ID, PRINT_DEBUGINFO, and GET_LE_FROM_BANKACCT_ID support tangible identification, diagnostic output, and derivation of the legal entity associated with a bank account.

Tables Accessed

The package reads and writes the principal IBY transaction tables through APPS synonyms. IBY_FNDCPT_TX_EXTENSIONS stores transaction extension rows, while IBY_SECURITY_SEGMENTS and IBY_SYS_SECURITY_SUBKEYS hold the segmented and keyed representations of secured data. IBY_TRXN_SUMMARIES_ALL maintains summary transaction information. Card and bank instrument data is drawn from IBY_CREDITCARD, IBY_CREDITCARD_ISSUERS_B, IBY_EXT_BANK_ACCOUNTS, and CE_BANK_ACCOUNTS.

Authorization and payer data is sourced from IBY_DEBIT_AUTHORIZATIONS, IBY_EXTERNAL_PAYERS_ALL, and IBY_EXT_PARTY_PMT_MTHDS, while receipt information is referenced from AR_CASH_RECEIPTS_ALL. Supporting tables include IBY_BEPINFO, IBY_BEPKEYS, and FND_APPLICATION for application context.

Usage Notes

IBY_FNDCPT_TRXN_PUB is typically invoked from Oracle Payments internal processing packages, payment adapter flows, and instrument customization logic rather than directly from end-user forms. Its dependency list includes IBY_FNDCPT_COMMON_PUB, IBY_PAYMENT_ADAPTER_PUB, IBY_CREDITCARD_PKG, and IBY_FNDCPT_SETUP_PUB, indicating that it is driven by higher-level funds capture orchestration. Custom extensions should call the documented extension and encryption routines rather than writing directly to the underlying tables, because the package enforces security segmentation and encryption consistency. Because the package is referenced by 49 other packages, changes to it carry broad impact across the payments module.