Search Results insert_batch_status_new




Overview
Explore in AI Chat

Overview

IBY_TRANSACTIONCC_PKG is a core PL/SQL package within the Oracle Payments (IBY) module of Oracle E-Business Suite. It encapsulates the transaction processing logic used by the credit card and funds capture infrastructure, managing the lifecycle of payment transactions as they move from open status through batching, transmission to the payment system, and final settlement. The package defines the status constants and request types that govern how transactions are grouped, submitted, and reconciled, and it provides the procedural interface used by concurrent programs and other IBY components to create, update, and close batches of credit card, EFT, and PDC (paper draft) transactions. The header identifies the source file as ibytxccs.pls and defines a suite of status constants (SUCCESS, COMMUNICATION_ERROR, BEP_FAIL, REQUEST_PENDING, SCHED_IN_PROGRESS, VOICE_AUTH_REQD, OPEN_BATCHED, BATCH_TRANSITIONAL, BATCH_PENDING) and request type constants (batch close, capture, credit, return, request, and batch request), establishing the vocabulary used across the module for transaction state management.

Key Procedures and Functions

The package exposes 36 documented procedures and functions. Central to batch construction are INSERT_BATCH_TXN, INSERT_BATCH_STATUS, and INSERT_BATCH_STATUS_NEW, which record transaction-to-batch associations and persist batch status transitions as a batch is assembled and tracked. INSERT_AUTH_TXN, INSERT_REV_RESULT, INSERT_OTHER_TXN, and INSERT_TIMEOUT_TXN handle the creation of various transaction result records — authorization and reversal outcomes, miscellaneous transaction types, and timeout events returned by the payment processor. INSERT_QUERY_TXN supports inquiry transactions.

  • VALIDATE_OPEN_BATCH — verifies that an existing open batch is eligible for further processing.
  • PREPARE_INSTR_DATA — assembles instrument and transaction data required before submission.
  • INSERT_EXTENSIBILITY — persists extensibility (flexfield/descriptive) attribute data linked to a transaction.
  • CHECKROWS — evaluates transaction rows against batch processing criteria.
  • GETMBATCHID, GETTID, GETTIDUNIQUECHECK — retrieve and validate batch and transaction identifiers.
  • GETNUMPENDINGTRXNS, GETORGID — supply pending transaction counts and organization context used during grouping.
  • UPDATEBATCHEDTRXNS, UPDATEBATCHQUERYTRXN, UPDATE_BATCH — update transaction and batch records as status changes are applied.

The declared record type trxnGroupCriteriaType identifies the grouping criteria applied when transactions are consolidated into a batch.

Tables Accessed

The package reads and writes the primary IBY transaction and batch tables: IBY_TRXN_SUMMARIES_ALL, IBY_TRXN_CORE, and IBY_BATCHES_ALL, along with the IBY_BATCHES_S and IBY_BATCHID_S sequences. Configuration and instrument data are drawn from IBY_CREDITCARD_ISSUERS_B, IBY_CC_ISSUER_RANGES, IBY_FNDCPT_SYS_CC_PF_B, and IBY_FNDCPT_USER_CC_PF_B. Payee and security context is resolved through IBY_PAYEE, IBY_PAYEE_SUBKEYS, IBY_SECURITY_SEGMENTS, IBY_SYS_SECURITY_SUBKEYS, IBY_TANGIBLE, and IBY_ECAPP.

Usage Notes

IBY_TRANSACTIONCC_PKG is typically invoked by Oracle Payments concurrent programs that build, submit, and close credit card and funds capture batches, and by the IBY forms and internal APIs that coordinate transaction state. It is referenced by 14 other packages, indicating its role as a shared service layer rather than an end-user entry point. Direct custom invocation should be avoided in favor of the supported IBY APIs; customizations should call documented procedures only and must respect the status and request-type constants declared in the specification.