Search Results iby_security_segments_s

Overview

The APPS.IBY_TRANSACTIONCC_PKG package body is a core component of the Oracle Payments (IBY) module in Oracle E-Business Suite 12.1.1 and 12.2.2. Its primary business function is to manage the lifecycle of credit card and payment transactions processed through the Payments Transaction subsystem, including insert, update, and query operations against transaction, batch, and summary tables. The package supports refund and reversal handling, extensibility attribute population, and authorization-related transaction insertions. It also provides low-level utility routines used across the payment transaction stack, such as batch identifier retrieval and pending transaction counts. Because it is classified as an API of type OTHER and is referenced by 14 other packages, it functions as an internal infrastructure package rather than an end-user-facing API. The package notably incorporates validation logic for open batches, ensuring that batches contain at least one transaction, that payee security keys are present when encrypted transactions exist, and that only a single currency is represented within a batch.

Key Procedures and Functions

The documented procedures and functions fall into several functional groups:

• Batch Validation and Status: VALIDATE_OPEN_BATCH, INSERT_BATCH_STATUS, INSERT_BATCH_STATUS_NEW, UPDATE_BATCH, and CHECKROWS support the validation and status management of transaction batches.
• Transaction Insertion: INSERT_AUTH_TXN, INSERT_REV_RESULT, INSERT_OTHER_TXN, INSERT_TIMEOUT_TXN, INSERT_BATCH_TXN, and INSERT_QUERY_TXN handle the insertion of authorization, reversal, timeout, batch, and query transactions.
• Batch and Transaction Updates: UPDATEBATCHEDTRXNS and UPDATEBATCHQUERYTRXN update transactions associated with batched and query operations.
• Utility and Lookup Functions: GETMBATCHID, GETTID, GETTIDUNIQUECHECK, GETNUMPENDINGTRXNS, and GETORGID retrieve batch IDs, transaction IDs, pending transaction counts, and organization identifiers respectively.
• Extensibility and Instrument Data: INSERT_EXTENSIBILITY and PREPARE_INSTR_DATA populate extensibility attributes and prepare instrument data for transaction processing.

These routines collectively support the transaction state machine within Oracle Payments, enabling correct handling of authorizations, reversals, and batch finalization. The package uses FND_LOG runtime level constants to support diagnostic logging.

Tables Accessed

The package reads and writes a range of Payments tables via APPS synonyms:

• IBY_BATCHES_ALL and IBY_BATCHES_S: batch header and batch sequence data, used for batch validation, status insertion, and updates.
• IBY_TRXN_SUMMARIES_ALL and IBY_TRXN_CORE: transaction summary and core transaction details, central to validation and currency checks.
• IBY_BATCHID_S: sequence source for batch ID generation via GETMBATCHID.
• IBY_CREDITCARD_ISSUERS_B and IBY_CC_ISSUER_RANGES: credit card issuer definitions and card range data for instrument preparation.
• IBY_FNDCPT_SYS_CC_PF_B and IBY_FNDCPT_USER_CC_PF_B: system and user credit card profile configurations used in validation set resolution.
• IBY_VALIDATION_SETS_B and IBY_VAL_ASSIGNMENTS (referenced in validation cursor): validation code packages and assignments for payee-level validation.
• IBY_PAYEE and IBY_PAYEE_SUBKEYS: payee definitions and subkey data.
• IBY_SECURITY_SEGMENTS and IBY_SYS_SECURITY_SUBKEYS: security key and segment information, relevant to encrypted transaction validation.
• IBY_TANGIBLE and IBY_ECAPP: tangible and electronic commerce application data used during transaction processing.

Usage Notes

IBY_TRANSACTIONCC_PKG is an internal infrastructure package. It is not typically invoked directly by end users or custom code; instead, it is called by higher-level Oracle Payments packages and concurrent programs that process credit card and payment transactions. The 14 dependent packages that reference it indicate it sits beneath the transaction processing stack. Typical invocation scenarios include batch submission, authorization processing, reversal handling, and query operations executed from the Payments Manager or via scheduled concurrent programs. Custom code should avoid calling this package directly, as its procedures are designed for internal orchestration and may assume specific context (such as open batch state and security key availability) that external callers cannot guarantee. Developers extending Oracle Payments should use the documented public APIs of the IBY module rather than this package body.