Welcome to the T24 Application Structure and Products

T24 Navigation and Environment D-2

T24 Navigation and Environment D-3
 T24 consists of the code base- which is the code for applications and services.

Enquiries, versions and Menus are built for different roles in a bank and the
configuration is created for a “Model” bank with best practice processes based on our
experience in implementations.

T24 Navigation and Environment D-4

 Enter your Username and Password to login to T24

T24 Navigation and Environment D-55

 This is the home page that you see as soon as you log in to browser. We will soon see
how we can customize the home page & the menus without writing a single line of
code

T24 Navigation and Environment D-6

 There are various methods of creating a record in T24.
The first method to input a new record is by typing the <Application name>
followed by a space and the function for input- ‘I’ , followed by another space
and the keys ‘F3’ in the command line.

The most frequently used method to input a new record is to click on the new
deal icon when the application is launched. In this illustration you have
launched the CUSTOMER application and a new customer can be input by
clicking the new deal icon.

If you are working in a classic mode then type in the <APPLICATION> I followed
by Ctrl+F+Enter .

T24 Navigation and Environment D-7

 After an application is launched, the user can input the ID and use any of the buttons
depending on the function to be invoked, viz Edit, View and Action
button(interchangeably referred to as function or operation).
EDIT Button - New record is displayed for input or existing record is opened for
amendment
ACTION Button - Record is displayed and Authorise, Delete, Reverse or Verify
operations enabled appropriately
VIEW Button - Opens a record in ‘See’ mode

This is an alternative method to giving the function along with the application and ID
in the command line of the Home Page

T24 Navigation and Environment D-8

 We see a sample record in the CUSTOMER application. The application name and the record
Id( Customer number) are displayed. Details of the CUSTOMER are filled into the various
fields.
The VALIDATE button is used to validate the data entered in the fields. Errors will be raised on
validation
The COMMIT button will commit the record and save the contents of the record into the
corresponding database table.
The HOLD button is useful, when the user does not want to commit the data entered into the
database, but at the same time does not want to lose the information input. The data input is
saved to be modified, committed or discarded later as per the user’s discretion.
The next set of buttons are Functions enabled on using the ACTION button for an existing
record ID. For a NEW record these will be disabled.
In T24, DELETE function is used to delete an unauthorized record. T24 will never re-generate
the ID of such a record. Once generated the ID is never re-used unless manually input by the
user.
The AUTHORISE function is to be used to authorise the record. An authorizer should be
different from the user who input the record.
Any record which has been authorized cannot be deleted and can be removed from the live
tables only by using the REVERSE function. This moves the record to history.
The button which looks like the NEXT button is used to verify a record. This is applicable only
for certain applications. In FOREX and MONEY.MARKET applications, deals are prepared orally
through brokers sometimes. When the written confirmations are later received, verify
function is used to record time and date of receipt of confirmation.

T24 Navigation and Environment D-9

 The Up arrow button is displayed when a function is applied on a record. This button is used to return
to the application

T24 Navigation and Environment D-9

 For additional information on any of the field in an application, click on the Field
Label and online helptext is displayed.

The button with the letter “i” is useful to invoke predefined context sensitive
enquiry. For example you may view additional information of the related customer
100295 by clicking on the Context Enquiry.

One significant and important feature in T24 is called multi value and sub value
facility. Multiple data can be stored in a field by dynamically expanding the field
during transaction input.

“+” symbol is used to for multi valuing a field. When the field name begins with GB,
it indicates a language multi value. For example the CUSTOMER may have short
name in different languages.

When the field name does not begin with GB, it indicates a multi value field. For
example a CUSTOMER may have multiple email IDs.

Sub Value – When a multi value field is made up of multiple values. For eg a
CUSTOMER may have a residence and an office address. The residence address is
composed of multiple lines that make up the address.

T24 Navigation and Environment D-10

T24 Navigation and Environment D-11
 After data is entered into a record, the Validate Button can be used to find out if
there are errors. Errors will be displayed with a link to the field containing the
erroneous data and must be corrected before the record is committed

The Commit button also invokes the Validations

T24 Navigation and Environment D-12

T24 Navigation and Environment D-13
 When a record is committed, Overrides may be raised. Overrides are warnings.

T24 Navigation and Environment D-14

 An override is a warning message generated to inform the Inputter about some data
that is input in the record and needs confirmation from the User for committing the
record with the given values.
For example, A customer wants to withdraw $100 from his savings account which has
a balance of $150. Assume that by T24 norms, the minimum balance in the savings
account should be $100. When transaction is input to debit $100, on committing it
T24 generates an override about the insufficient funds available.

Override Messages are displayed with the Accept Override link and this must be
clicked to store the record in the database. The override message is stored as part in
the OVERRIDE field as part of the record.

If you do not want to accept the Override, you may either put the record on hold to
correct it later or amend the record and commit it again.

T24 Navigation and Environment D-15

15
T24 Navigation and Environment D-16
16
T24 Navigation and Environment D-17
17
T24 Navigation and Environment D-18
 Go to role based home page in the T24 menu and check out the home pages
customized according to role of the bank employees . Shown here is a sample home
page for a Head Teller.

T24 Navigation and Environment D-19

 COMPANY table holds one record per company created in the installation.
The company mnemonic is used as the table prefix.
The ID of a record in the COMPANY table is referred to as the company code in T24.
The format is CCGGGLLLL Where: CC is Country Code GGG is Company Group Code
and LLLL is Local Code. For example GB-001-0001

T24 Navigation and Environment D-20

 LOCAL COUNTRY : This field holds the country code where the company is situated.
LOCAL REGION : This field identifies the region in the country in which the company is
physically situated.
LOCAL CURRENCY : This field holds the local currency of the company.

APPLICATION : The Bank may restrict the access of applications to different

companies. A company may have access to a set of applications only. This field holds
the various applications that are installed in the company. Different companies of a
bank may have different set of applications installed.

FINANCIAL YEAR END : This field holds the current financial year end date and the
frequency from there on.

Sharing of tables among different branches can also be set in COMPANY application

T24 Navigation and Environment D-21

 This illustration shows how tables are shared by different branches based on what
information they hold – customer, financial or installation parameters.

CUS CUSTOMER and COLLATERAL are “CUS” type of tables . A branch may opt to
share it with other branches or have its own data.
FIN Financial tables like ACCOUNT and FOREX are not shared among branches. Each
branch maintains its own data.
INT Installation tables like DATES, SPF only hold information that can be used across
branches and hence shared by all branches.

T24 Navigation and Environment D-22

 • T24 maintains and uses its own dates.
• T24 does not consider the system date but date from the DATES table. However
some applications consider the system date. For example, in the USER application
START.DATE.PROFILE field takes into consideration the current systemdate and not
T24 date.
• DATES application is used to define the dates for the previous, the current and the
next working day
• The DATES table need not be manually updated to change the current working day.
Dates are rolled forward automatically during the Close Of Business process.
• All Companies defined in T24 will have a record in DATES table. ID of a record in
DATES is COMPANY.ID
• DATES is an INT type of table and therefore the table name at database level is
F.DATES.
• Holidays are stored in another table, which will be discussed as we proceed

T24 Navigation and Environment D-23

 The DATES application is used to store the previous, the current and the next
working day. When the dates are rolled forward, only working days are
considered.
The ID of a record in DATES table is the Company code.
TODAY : This field denotes the current T24 date.
LAST WORKING DAY : This field holds the date of the previous working day
before COB was run.
NEXT WORKING DAY : This field holds the date of the next working day with
respect to today.
The values in the above 3 fields will be updated during COB.
Values for these fields are populated during Close of Business after referring to
the HOLIDAY table (To be discussed next).
Every transaction in T24 will contain a ‘Value Date’ which refers to the date on
which the transaction will affect the banks books of accounts. Some T24
modules support a backward or a forward value date. The maximum back
value and forward value possible is stored here.
BACK VALUE MINIMUM : This field specifies the minimum back value date for
a transaction.
BACK VALUE MAXIMUM : This field specifies the maximum back value date.
FORWARD VALUE MINIMUM : This field specifies the minimum forward value
date.
FORWARD VALUE MAXIMUM : This field specifies the maximum forward value
date.

T24 Navigation and Environment D-24

 VERSION, LOCAL PAYMENT DAY and LOCAL DISPO DAY fields are reserved for future use and are not
used currently.

T24 Navigation and Environment D-24

 1. The purpose of the HOLIDAY table is to indicate the public holidays for each
Country, or Region within a Country.
2. HOLIDAY is an INT type of table and therefore the table name at database
level is F.HOLIDAY.
3. This table is referred during COB to determine T24’s next working day.
4. This table is also referred by T24 to check for holidays and weekend days
when dates are input in any transaction.
5. The ID of a record in this table is in the format <CountryCode RegionCode
Year>. For example GB 00 2010, AT 00 1988, etc..

Even before you set up a record in the HOLIDAY application, the REGION and
COUNTRY tables must be set up since they are part of the record ID.

T24 Navigation and Environment D-25

 To set a particular day as a holiday in a month, the following fields are used
JANUARY – DECEMBER : These fields hold the days that need to be declared as holidays in the
respective months. Valid values are 01 until 31 (if applicable). Space is the delimiter.
WEEKEND DAYS : This is a Multi value field that is used to define the days that are weekends.
Valid input will be any of the days from Monday to Sunday
MTH 01 TABLE - MTH 12 TABLE : These fields are no input fields. These are populated based
on values in fields JANUARY - DECEMBER, WEEKEND DAYS and WRK WKND JANUARY - WRK
WEEKEND DECEMBER. This field can hold H W X as values. H stands for Holiday, W stands for
Working day and X stands for No more days in the month.
WRK WKND JANUARY - WRK WEEKEND DECEMBER : These fields holds the days which are
actually weekend days but to be declared as working days for each month. Valid values are 01
to 31 (if applicable)
It is not possible in T24 to declare Current day and the next day as holidays. T24 needs at least
one day time to declare a working day as a holiday. For example, if today is 9th Jan and
tomorrow is 10th Jan, you cannot set both 9th and 10th as holidays in T24. On 9th Jan you
can only set 11th Jan and above days as holidays.
If there is any unforeseen situation and you have to declare a holiday during the middle of the
day on 9th Jan, then the Administrator should run COB for 9th Jan before closing so that the
dates are rolled over to 10th Jan which is the next working day.
If there is a situation that you have to set 10th Jan as a holiday on 9th Jan, then the
Administrator has to run COB both for 9th Jan and 10th Jan so that the dates are rolled over
to 11th Jan which is the next working day. Running COB back to back blindly may not solve
this issue. Certain applications may require local development. If transactions come in
through interfaces or ATMs on the physical 10th Jan, they will be taken as transactions for
11th Jan only as T24 date has already been rolled forward.
In typical situations, COB can also be run remotely by an Administrator.

T24 Navigation and Environment D-26

 Some of the important fields are discussed in this unit.
RUN DATE : This field holds the server date when the COB was run last time.
SITE NAME : This field holds the name of the installation at which T24 is installed.

CURRENT RELEASE : This field holds the current T24 release. It’s a no input field.
HIST LIFE : This field defines the number of days for which the exception log in
EXCEPTION.LOG.HIST file should be retained. EXCEPTION.LOG.FILE is used to log activities or
business validation exceptions encountered by the applications run by the framework. This
file was primarily used to log exceptions from within any process where there was no user
interaction or where it was not possible to throw the exception at the user for the user to
make a decision. Initially it was for end of day batch jobs but with the new service oriented
architecture, it may as well apply for online services (TSA Services) running at the back-
ground.

CACHE EXPIRY : This field specifies the time interval in seconds before the cache file refreshes.

Enquiry is a request to view data of a record from the database level.

ENQ PAGE LIMIT : The maximum number of pages of output of an enquiry that can be
viewed. Irrespective of this value, at the time of printing, all pages of output will be printed.

T24 Navigation and Environment D-27

 Some of the important fields are discussed in this unit.
RUN DATE : This field holds the server date when the COB was run last time.
SITE NAME : This field holds the name of the installation at which T24 is installed.

CURRENT RELEASE : This field holds the current T24 release. It’s a no input field.
HIST LIFE : This field defines the number of days for which the exception log in
EXCEPTION.LOG.HIST file should be retained. EXCEPTION.LOG.FILE is used to log activities or
business validation exceptions encountered by the applications run by the framework. This
file was primarily used to log exceptions from within any process where there was no user
interaction or where it was not possible to throw the exception at the user for the user to
make a decision. Initially it was for end of day batch jobs but with the new service oriented
architecture, it may as well apply for online services (TSA Services) running at the back-
ground.

CACHE EXPIRY : This field specifies the time interval in seconds before the cache file refreshes.

Enquiry is a request to view data of a record from the database level.

ENQ PAGE LIMIT : The maximum number of pages of output of an enquiry that can be
viewed. Irrespective of this value, at the time of printing, all pages of output will be printed.

T24 Navigation and Environment D-28

 1. True
2. False – Errors must be corrected. Record cannot be committed otherwise
3. False – Mnemonic is prefixed for CUS and FIN tables
4. False – Holiday table
5. True
6. False - FIN tables are not shared since they contain Financial information
specific to one company only.

T24 Navigation and Environment D-29

T24 Navigation and Environment D-30