top of page
Search

Core Concepts in Temenos T24

  • Writer: Josef Mayrhofer
    Josef Mayrhofer
  • 2 days ago
  • 3 min read

To grasp the fundamental concepts of T24 core banking, it is essential to connect them with our everyday banking practices. A straightforward example is a balance inquiry, which involves retrieving the balance stored in the database. Another example is the transfer of funds, which functions as both a debit and credit update, representing a write operation to the database. In this blog, we will share the basic concepts of T24 core banking.


  1. Applications


 An application is a module that defines various banking activities. For instance, ACCOUNT is one application, while CUSTOMER is another. These applications can be core, provided by Temenos, or local, designed by individual banks. The values for these applications are stored in different fields within the database.


Version: A version represents a customized appearance of an application. If the CUSTOMER application contains 150 fields, the version application can be tailored to include only the necessary fields and mandatory ones. This constitutes a WRITE operation to the database.


Enquiry: The term enquiry indicates that we are seeking information about an application with specific fields. This is a READ operation to the database. There are various types of enquiries, such as FILE, NOFILE, DRILLDOWN, FASTPATH, and CONTEXT, which allow us to define and retrieve values accordingly.


Parameter files: These are built-in T24 files that support applications and other activities within T24. Examples include SPF, PGM.FILE, and FILE.CONTROL. Each file serves its own distinct function.


  1. OFS: Open Financial Services


OFS serves as the medium through which T24 interacts both internally and externally. You can transmit your transaction in the OFS format to T24 and obtain the response in the identical standardized OFS format.


OFS Write or Update 


We use Transaction requests when we update or write information to T24.


Below is a sample OFS TRANSACTION request:


ENQUIRY.SELECT, T24SIGNONNAME/PASSWORD,ENQUIRY.NAME,SELECTION.CRITERIA

Ex: ENQUIRY.SELECT,,INPUTT/PASSWORD,%INDUSTRY


  1. COB And Services


JOB: The fundamental unit of COB is the JOB, which can encompass a program, routine, or enquiry report.


BATCH: A Batch is a collection of JOBS that determines their scheduling, such as Daily, Weekly, Monthly, during COB, or ADHOC (Outside COB).


SERVICE: The Service component governs whether a BATCH can be initiated or halted. It is necessary to establish a service for each batch.


COB: COB represents a combination of multiple jobs organized through Batches and structured into five stages. All banks need to execute COB at the end of each working day.


  1. User


Security Management System in T24 deals with aspects like:

  • Who can log in to T24?

  • How can they log in?

  • When can they log in?

  • What can they do after login?

  • How long can they be active?


 A specialized application called USER is designed to answer all the above questions. Let's get into the main fields and their functionality of USER application.


  • USER NAME: Actual user name who is using the T24

  • SIGN ON NAME: This is the screen login name.


  1. Programming


The releases of Globus and TAFC primarily utilize the INFOBASIC programming language, with most core tables developed using this logic.


In contrast, the TAFJ releases employ INFOBASIC, Componentized, and Java programming languages. Additionally, the extensibility framework incorporates Python coding. Depending on the specific release and client requirements, banks can choose the programming language.


  1. Interfaces


These are the third-party applications that connect with T24 for daily activities.


The ATM interface serves as an intermediary layer between the ATM switch and Temenos Transact. This interface includes a plug-in for the application server, enabling it to receive messages through a dedicated port and convert ISO messages. The application server transmits the ISO message to Temenos Transact, where it is transformed into OFS message format according to the mapping files defined in the interface.


 Once the transaction is finalized in Temenos Transact, the response ISO messages are formatted within the ATM interface's parameters. These response messages are marked with the appropriate error or success status, reflecting the reply status from the Temenos Transact application as specified in the framework.


Similarly, all other interfaces are ultimately linked to T24 via OFS.

 

Our T24 Training course encompasses all fundamental concepts of T24. If you would like to learn more about this topic, feel free to contact us at Performetriks. We look forward to helping you out.

Happy Performance Engineering!



Comments

bottom of page