Batchquery Successful But Leaves IBY_TRXN_SUMMARIES_ALL.STATUS At 111
(Doc ID 431810.1)
Last updated on MARCH 04, 2019
Applies to:Oracle Payments - Version 18.104.22.168 to 22.214.171.124 [Release 11.5]
Information in this document applies to any platform.
Running Scheduler concurrent program with BATCHQUERY option, the concurrent request completes successfully. While the batch is updated to a complete status, the transactions are not updated.
-- The issue can be reproduced at will with the following steps:
1. Run iPayment Scheduler with BATCHQUERY option to pick up response files from FDC server
2. Check IBY_BATCHES_ALL.batchstatus and IBY_TRXN_SUMMARIES_ALL.status columns
-> IBY_BATCHES_ALL.batchstatus will show 0
-> But IBY_TRXN_SUMMARIES_ALL.status still shows 111
-- Expected Behavior:
Expect both IBY_BATCHES_ALL.batchstatus and IBY_TRXN_SUMMARIES_ALL.status to change to 0 after successful batchquery.
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