Search Results iby_batches_s




Overview
Explore in AI Chat

Overview

IBY_TRANSACTIONSET_PKG is a PL/SQL package body owned by the APPS schema in Oracle E-Business Suite. It belongs to the Payments (IBY) module and supports the transactional foundations of Oracle Payments by managing the creation, status tracking, and summarization of payment transactions and their associated batches. The package operates within the transaction-set layer that underlies Oracle Payments processing, where groups of payment instructions are staged, validated, authorized, and finally settled. Because the object is a package body with no declared specification exposed to other schemas, it is intended primarily as an internal implementation unit invoked by other IBY components rather than as a public API for external integration.

The user search term "iby_batches_s" corresponds to the IBY_BATCHES_S sequence, which the package body references. This dependency confirms that IBY_TRANSACTIONSET_PKG is responsible for generating surrogate primary keys for batch header records at the time batch-level transaction rows are inserted into the transaction tables.

Key Procedures and Functions

The documented interface exposes nine procedures and functions, each tied to a specific stage of the payment transaction lifecycle:

  • INSERT_INIT_TXN — Creates the initial transaction record for a payment session or instruction, seeding the core transaction data before further attributes are populated.
  • INSERT_SET_TXN — Inserts transaction-set entries, associating individual transactions with the batch or set to which they belong.
  • INSERT_AUTH_TXN — Records authorization events, capturing the point in the lifecycle where a transaction is approved or accepted for processing.
  • INSERT_OTHER_TXN — Handles miscellaneous transaction types not covered by the more specific insert routines.
  • INSERT_TIMEOUT_TXN — Persists transactions that reach a timeout condition, enabling downstream reconciliation and exception reporting.
  • INSERT_BATCH_STATUS — Writes or updates batch-level status information, tracking the progress of a payment batch through its stages.
  • INSERT_BATCH_TXN — Inserts transaction records explicitly linked to a batch, drawing the batch identifier from the IBY_BATCHES_S sequence.
  • INSERT_QUERY_TXN — Creates transaction entries for query or inquiry processing, retaining traceable records for audit purposes.
  • FIND_PARENT_SPLITID — A lookup routine that resolves the parent split identifier, supporting the hierarchical relationship between split payment instructions and their originating transactions.

Tables Accessed

The package reads from and writes to several core Payments tables through APPS synonyms. IBY_BATCHES_ALL and IBY_BATCHES_S provide the batch header records and their sequence-generated identifiers. IBY_TRXN_CORE and IBY_TRXN_EXTENDED store the primary and extended attributes of each payment transaction. IBY_TRXN_SUMMARIES_ALL, IBY_TRXNSUMM_MID_S, and IBY_TRXNSUMM_TRXNID_S support transaction summarization and its key generation. IBY_PAYEE supplies payee information, IBY_TANGIBLE holds tangible payment details, and DUAL is used for single-row utility queries. The package also calls sibling packages including IBY_BILL_PKG, IBY_ACCPPMTMTHD_PKG, IBY_TRANSACTIONCC_PKG, and its own specification for encapsulated logic.

Usage Notes

IBY_TRANSACTIONSET_PKG is not referenced by any other database object, which indicates it is invoked indirectly—typically from Oracle Payments forms, concurrent programs such as payment instruction creation and formatting, or custom extensions that mirror the standard transaction-building workflow. The presence of insert routines for initialization, authorization, batching, timeout, and querying suggests the package is called at multiple points during the payment lifecycle. Developers extending Oracle Payments should treat this body as an internal reference and avoid direct dependencies, since package bodies carry no contract guarantees across patches or upgrades.