Search Results secure_wipe_segment

Overview

IBY_FNDCPT_TRXN_PUB is the public transaction-processing API within the Oracle Payments (IBY) module, the payment engine shared across Oracle E-Business Suite release 12.1.1 and 12.2.2. The package exposes the core business operations required to create, maintain, authorize, settle, and reverse payment transactions originating from external-facing channels such as credit cards, debit authorizations, and bank account transfers. In practice it is the programmatic backbone behind iPayment-style flows, serving as the contract between Oracle EBS application modules and the underlying funds capture data model.

The package is owned by APPS and classified as a public (PUB) API, meaning its signatures are intended to remain stable for external consumers. It is referenced by 49 other packages, confirming its role as a foundational dependency rather than a leaf utility. Constants such as G_RC_AUTH_SUCCESS, G_RC_AUTH_PENDING, and G_RC_INVALID_AMOUNT form a standardized result-code vocabulary that callers use to interpret outcomes without parsing messages.

Key Procedures and Functions

The 26 documented routines fall into several functional families:

• Transaction extensions: CREATE_TRANSACTION_EXTENSION, UPDATE_TRANSACTION_EXTENSION, GET_TRANSACTION_EXTENSION, COPY_TRANSACTION_EXTENSION, and DELETE_TRANSACTION_EXTENSION manage the flexible attribute framework that carries supplementary transaction data.
• Authorization: CREATE_AUTHORIZATION, GET_AUTHORIZATION, and CANCEL_AUTHORIZATION handle funds authorization requests and their lifecycle.
• Settlement and returns: CREATE_SETTLEMENT, CREATE_SETTLEMENTS, CREATE_RETURN, and CREATE_REVERSAL process captured funds, returned items, and reversals.
• Security: SECURE_WIPE_SEGMENT, ENCRYPT_EXTENSIONS, ENCRYPT_SECURITY_CODE, DECRYPT_EXTENSIONS, and GET_SECURITY_CODE protect sensitive cardholder and segment data.
• Lookup and diagnostics: GET_TANGIBLE_ID, GET_LE_FROM_BANKACCT_ID, and PRINT_DEBUGINFO support identifier resolution and troubleshooting.

GET_TANGIBLE_ID is the routine most relevant to a search on that term. It resolves the tangible identifier associated with a payment transaction — the concrete instrument reference used by downstream settlement and reconciliation logic. GET_LE_FROM_BANKACCT_ID performs the analogous derivation of a legal entity from a bank account identifier.

Tables Accessed

The package reads and writes a broad set of APPS-synonym tables. IBY_FNDCPT_TX_EXTENSIONS stores transaction extension rows, while IBY_SECURITY_SEGMENTS, IBY_SYS_SECURITY_SUBKEYS, and IBY_CREDITCARD back the encryption and security-code routines. Authorization and settlement data reside in IBY_DEBIT_AUTHORIZATIONS, IBY_TRXN_SUMMARIES_ALL, and AR_CASH_RECEIPTS_ALL. Bank and payer information is drawn from CE_BANK_ACCOUNTS, IBY_BEPINFO, IBY_BEPKEYS, IBY_EXTERNAL_PAYERS_ALL, IBY_EXT_BANK_ACCOUNTS, and IBY_EXT_PARTY_PMT_MTHDS. IBY_CREDITCARD_ISSUERS_B and FND_APPLICATION supply reference and application context data.

Usage Notes

IBY_FNDCPT_TRXN_PUB is normally invoked by other IBY packages and by Oracle Payments forms during funds capture processing, rather than directly by end users. Custom integrations that process credit card or bank transfer transactions call these routines to register authorizations, settlements, and reversals against the standard data model. Because the package is classified PUB and referenced by 49 other packages, changes should be treated as high-impact; custom code should rely on the documented result-code constants and avoid direct DML against the underlying tables.