KEMBAR78
Introduction | PDF
Scribd
Upload
41 views1 page

Introduction

The document discusses a common error faced by T24 Java developers when trying to access high-volume tables, which is enforced by the Temenos framework. It details a solution involving the modification of the EB_DataAccessApi.jar file to bypass this restriction, allowing for direct access to tables like TELLER$HIS and STMT. The author aims to provide technical insights on this enhancement to improve data retrieval flexibility in T24.

Uploaded by

Khaled Ghalab
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
41 views1 page

Introduction

The document discusses a common error faced by T24 Java developers when trying to access high-volume tables, which is enforced by the Temenos framework. It details a solution involving the modification of the EB_DataAccessApi.jar file to bypass this restriction, allowing for direct access to tables like TELLER$HIS and STMT. The author aims to provide technical insights on this enhancement to improve data retrieval flexibility in T24.

Uploaded by

Khaled Ghalab
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 1

Wednesday, March 19, 2025 2:38 PM

Introduction

Every T24 Java developer has likely encountered the following error when attempting to select
records from certain high-volume tables:

"Error retrieving TELLER$HIS records: EB-INTERNAL.ERROR T24CoreException An internal


error occurred, the message is: Select on TELLER$HIS is disabled as it is high volume."

This restriction applies to multiple tables, including STMT.ENTRY, SEC.TRADE, TELLER$HIS,


FUNDS.TRANSFER$HIS, and others. The Temenos framework enforces these limitations, preventing
direct queries and causing significant challenges for developers working with large datasets.

To bypass this restriction, I analyzed the EB_DataAccessApi.jar file, decompiled it, and modified the
EB_SYSTEM_SELECT_RECORDS_cl.class. By editing this class, I removed the enforced blocking
mechanism, allowing direct access to these high-volume tables. This modification provides greater
flexibility for data retrieval within T24.

Let’s explore the technical details and how this enhancement improves accessibility.

In the COMO file you could see the ERROR below

I've google it to find any solution, I got people also talking about same issue

Here is the method explanation and the blocked tables

New Section 4 Page 1

You might also like