Search Results insert_set_txn




Overview
Explore in AI Chat

Overview

IBY_TRANSACTIONSET_PKG is an Oracle Payments (IBY) PL/SQL package in the APPS schema that persists payment transaction records generated by the Oracle Payments transaction set framework. Its central responsibility is the controlled insertion of transaction rows into the IBY summary and detail tables as external vendor or biller applications return results for each stage of a payment instruction lifecycle. Rather than relying on a single generic write path, the package exposes discrete procedures per transaction type so that the correct columns, status values, and extended attributes are populated for each event class found in the IBY data model.

The header comment embedded in the source identifies the package version ($Header: ibytxsts.pls 120.2) and states that the SET INIT procedure is intentionally non-idempotent: it inserts a new transactions row only after the vendor application has responded, and it performs no duplicate check because the caller is expected to have invoked query-set validation (such as ListVendor) beforehand. This design places responsibility for pre-validation with the calling program while keeping the insert path lean.

Key Procedures and Functions

The documented package contains nine procedures and functions:

  • INSERT_INIT_TXN — Records a SET INIT transaction after the vendor application returns, creating the initial row for the transaction set. It carries the widest parameter surface in the package, reflecting the number of attributes captured at initiation (application, payer/payee identifiers, amount and currency, status, instrument name, tangible order details, and organizational context).
  • INSERT_SET_TXN — Inserts a transaction row for a standard SET operation within an existing transaction set.
  • INSERT_AUTH_TXN — Persists authorization transaction results returned by the payment system or vendor.
  • INSERT_OTHER_TXN — Records transactions that fall outside the standard initiation, set, and authorization categories.
  • INSERT_TIMEOUT_TXN — Captures the outcome when a transaction attempt expires or fails to respond within the expected window.
  • INSERT_BATCH_STATUS — Writes batch-level status information, linking transaction processing back to the batch record. This is the procedure most commonly searched when tracing how batch status is recorded in IBY.
  • INSERT_BATCH_TXN — Inserts transaction rows associated with a batch-level processing event.
  • INSERT_QUERY_TXN — Records the result of a query transaction issued against a vendor or biller.
  • FIND_PARENT_SPLITID — Resolves the parent split identifier, supporting hierarchical relationships between split transactions and their originating rows.

Tables Accessed

The package operates against the following documented tables and views via APPS synonyms:

  • IBY_TRXN_SUMMARIES_ALL — The primary destination for transaction summary rows; populated by most insert procedures.
  • IBY_TRXN_CORE — Stores core transaction attributes such as instrument name and identifiers.
  • IBY_TRXN_EXTENDED — Holds extended attributes not present in the core transaction record.
  • IBY_TANGIBLE — Provides tangible order details including biller account number, reference information, memo, order medium, and EFT authorization method.
  • IBY_BATCHES_ALL / IBY_BATCHES_S — Batch header table and its sequence, used when recording batch and batch-status transactions.
  • IBY_PAYEE — Supplies payee identification data.
  • IBY_TRXNSUMM_MID_S — Sequence used to generate transaction summary identifiers.
  • IBY_TRXNSUMM_TRXNID_S — Sequence used to generate transaction identifiers.
  • DUAL — Used for single-row expressions such as sequence retrieval.

Usage Notes

IBY_TRANSACTIONSET_PKG is an internal API classified as OTHER and is referenced by zero other packages in the documented metadata, indicating that it is invoked directly by Oracle Payments runtime components rather than layered beneath other PL/SQL units. It is typically called from the payment processing and transaction set coordination logic that communicates with external vendor applications, and from forms or concurrent programs that must record batch status, timeouts, and authorization results.

Because INSERT_INIT_TXN performs no duplicate checking and is not idempotent, custom code calling this package must first verify that a transaction row does not already exist, normally through query-set ListVendor validation. Callers should also supply the organization context (org_id) and instrument identifiers to ensure multi-org and payment instrument integrity. Substitution variables, if required, should be defined in the calling script as they are not resolved by the package itself. Direct updates to the underlying IBY tables are not recommended; the insert procedures should be used so that sequence-generated identifiers and required columns are populated consistently.