Search Results g_status_success

Overview

The APPS.IBY_BANKPAYMENT_UPDT_PUB package body provides the public status-maintenance interface for Oracle Payments (IBY) bank payment processing in Oracle E-Business Suite 12.1.1 and 12.2.2. Its central responsibility is to persist state transitions on payment batches, individual payments, and query (batch status inquiry) operations as they move through the bank payment lifecycle — from formatting through confirmation, cancellation, submission to a payment processor, or failure. The package exposes a small set of published procedures that internal IBY components and external callers use to record the outcome of payment processing activity against the core IBY tables.

The package declares a series of package-level constants that map to the internal IBY utility status codes. Among these is G_STATUS_SUCCESS, defined as IBY_UTILITY_PVT.STATUS_SUCCESS. A search for g_status_success therefore typically indicates a developer tracing how a successful processing outcome is represented and returned through this package's status-update logic. Because these constants are declared with CONSTANT, they provide a stable, readable alias for the numeric status values used throughout IBY, and they are referenced when a procedure must set or validate a terminal success state on a batch, payment, or query record.

Key Procedures and Functions

The package exposes five documented procedures:

• UPDATEBATCHSTATUS — Updates a payment batch record with a new batch status value, along with any associated error code and error message. Documented batch status values include Submitted to Processor, Request not supported, Scheduler in progress, Communication error, Formatted, Confirmed, Canceled, and Batch Failure. This is the primary status-transition routine for IBY_PAY_BATCHES_ALL.
• UPDATEECBATCHES — Handles status maintenance for electronic-commerce batch records, keeping batch-level state consistent across the IBY batch model.
• UPDATETRXNSTATUS — Updates the status of an individual payment transaction, reflecting the result of processing, confirmation, or failure at the payment level.
• SETBATCHFAIL — Marks a batch as failed, applying the failure state and any accompanying error information.
• UPDATEQUERYSTATUS — Records the outcome of batch status inquiry operations, using the query-oriented status codes (partially processed, failed, or pending) declared within the package.

The package's status constants — including G_STATUS_SUCCESS, G_STATUS_BEP_ERROR, G_STATUS_BATCH_PARTIAL, and the query-specific codes — are used internally to classify outcomes passed to these procedures.

Tables Accessed

The package reads and writes the following documented tables through APPS synonyms:

• IBY_PAY_BATCHES_ALL — The primary target for batch status updates and error code/message capture, including the batch identifier used as the key parameter.
• IBY_PAY_PAYMENTS_ALL — The payment-level table updated when transaction status changes are recorded.
• IBY_BATCHES_ALL — The broader IBY batch table whose status is synchronized for electronic-commerce and batch-level operations.

Usage Notes

This package is an API-classification public package, intended for invocation from IBY processing components that execute during bank payment batch formatting, transmission, confirmation, cancellation, and status inquiry. It is typically called by concurrent programs and internal IBY flows that own the payment lifecycle, and it may be invoked from custom code or forms that need to reflect the latest processing state of a batch or payment. Because it is documented as referenced by zero other packages, its callers are primarily runtime processing units rather than other PL/SQL packages. Callers should supply valid batch or payment identifiers and the appropriate numeric status from the IBY utility domain to ensure downstream reporting and reconciliation reflect accurate state.