My Oracle Support Banner

Fetch Settlement Batch Clearing Request Leaves An Invalid Combination Of TRANSACTION STATUS 111 And BATCHSTATUS 0 In IBY Tables (Doc ID 3079235.1)

Last updated on MARCH 28, 2025

Applies to:

Oracle Payments - Version 12.1.3 and later
Information in this document applies to any platform.

Symptoms

After running "Fetch Settlement Batch Clearing," the IBY tables show an invalid TRX STATUS and BATCHSTATUS combination:

Table iby_trxn_summaries_all: STATUS is 111 for all the transactions of the processed batch.

Table iby_batches_all: BATCHSTATUS is 0 for the processed batch.

 

While a BATCHSTATUS of 0 suggests successful batch processing, this is contradictory because a TRANSACTION STATUS of 111 indicates the transactions within the batch were not yet processed.

This issue might occur when a payment system, like Paymentech, provides an invalid or corrupted ACK (acknowledgement) file.

It's crucial to understand that even with a bad ACK, the payment system might have still processed the funds, but the confirmation (acknowledgement) was not properly delivered. 

 

Steps to reproduce:

1. Login with responsibility: Funds Capture Process Manager

2. Run "Fetch Settlement Batch Clearing" with an invalid/corrupted ACK (Acknowledgment) file provided by your payment system.

 

Queries to identify the issue:

select * from iby_trxn_summaries_all where batchid = '&enter_affected_batch_id';

select * from iby_batches_all where batchid = '&enter_affected_batch_id';

 

There are multiple consequences of this issue:

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.