T24 Directory Structure & File System

Objectives

At the end of the session you will have

 Adequate knowledge to understand

 T24 directory structure
 File types in T24
 File classification in T24

Slide 2
T24 Directory Structure
bnk

bnk.data bnk.dict bnk.run bnk.help bnk..jnl bnk.backup

ac fx eb globusbin globuslib bin lib

 bnk is the parent directory

 bnk.data : Holds all the data files of T24. Contains subdirectories. Each of the subdirectories
refer to the various products installed. Data files of applications are stored under the
appropriate subdirectories
 bnk.dict : Holds all the dictionary files of all applications in T24
 bnk.run : Home directory for all t24 users. Contains globusbin, globuslib which store the
business logic of T24. Bin and lib are used to store any local dev business logic
 bnk.help : Directory where help files are installed
 bnk.jnl : Holds the F.JOURNAL file which is an application level log file that captures all data
input in T24. Only the last 20 transactions data are stored in this file. Journaling is achieved by
using jBASE Transaction Journaling if j4 is the database.
 bnk.backup : If desired, backup of T24 can be stored here.

Slide 3
File Types

 User inputs and commits a record in the CUSTOMER application

 File that gets updated : FBNK.CUSTOMER$NAU

 User authorizes the record in the CUSTOMER application

 Files that get updated
Record deleted from FBNK.CUSTOMER$NAU
Record written to FBNK.CUSTOMER

Slide 4
File Types

 User amends the authorized CUSTOMER record (Record becomes

unauthorized again)
 Files that get updated
Record written to FBNK.CUSTOMER$NAU (Amended record)
The authorized record remains in the FBNK.CUSTOMER file

 User authorizes the amended CUSTOMER record

 Files that get updated
Record deleted from FBNK.CUSTOMER$NAU
Amended record written to FBNK.CUSTOMER
Previously authorized record moved to FBNK.CUSTOMER$HIS

Slide 5
File Types (Cont.)

 Valid file types

 Live file – Holds only authorized records

 Unauthorized file ($NAU)

INAU,INAO,INA2,RNAU,RNA2,RNAO,IHLD

 History file ($HIS) – Holds copies of authorized records

ID format : <Record ID>;<Sequence Number>

 Most of the applications support all the 3 types of files

Slide 6
File Types

 List authorized CUSTOMER records

 List unauthorized CUSTOMER records

 List CUSTOMER history records

Slide 7
Workshop

 List the Live and Unauthorized records for the ACCOUNT Application.

Slide 8
File Classification in T24

Slide 9
A Decision The Bank Must Make

 All banks have branches, T24 calls them companies

 T24 supports multi-company operations

 When the bank gets the tape containing T24 from Temenos, there is
only one company defined - Head Office.

 As part of the implementation process, as many companies as required

can be created

 Before creating companies, a decision on the following have to be

made
 Local currency of each company
 Company Name and Mnemonic

Slide 10
Companies

 We can create two types of companies in T24

 Lead Companies – These types of companies have their own set of
file to store financial information

 Branch Companies – These types of companies share an existing

Lead Company’s files

 If the T24 installation has branches around the world that use different
local currency, then, within T24, we must define that many number of
Lead Companies

 Branch companies share the files of a Lead company if they use the
same local currency

 Remember, Lead and Branch companies will each have a record in the
COMPANY application

Slide 11
Lets Discuss Important Fields In The COMPANY File

ID : Holds the ID of the Company

Mnemonic : Holds the mnemonic of the

company

CUSTOMER.COMPANY : Holds the ID

of the company which stores CUS type
of files.
If each of the companies have their own
copy of CUS type of files, then, the value
in this field will be respective company
code.
If companies are to have a common
copy of CUS type of files, then, each of
the companies will have the ID of the
company that is actually storing the files.
FINANCIAL COM : All lead companies
have there own FIN files and will always
have different values in the field
FINANCIAL COM

Model Bank has only one LEAD company

record defined at first

Slide 12
T24’s bnk.data Directory

 All files that T24 uses to store data are in ‘bnk.data’

 bnk.data is part of T24’s directory structure

 There is only one such directory per installation of T24 and it does not
depend on of companies

 Will each company in T24 have its own set of files in bnk.data ?
 No - only LEAD companies

Slide 13
T24 Application Classification

 T24’s Applications are broadly divided into three main types

 CUS
 FIN
 INT
 Information about this classification is available in the FILE.CONTROL
application in the CLASSIFICATION field

Slide 14
CUS Files

 CUS type applications

 These applications store customer related data

 These types of files are shared between a Lead Company and its
branches

 Different Lead companies can also share the same files

 Because of this, the names of the files for this type of applications
follow this syntax F<MNEMONIC>.<APPLICATION>

 The company mnemonic is part of the file name because if each

company has its own file, we must be able to tell which company
each file belongs to
Example: FBNK.CUSTOMER

Slide 15
FIN Files

 FIN type applications

 These applications hold financial data

 A Lead Company will have its own set of FIN files and all its
branches will access the same

 Lead companies cannot share FIN files, they must have there own
copy

 These applications follow the file naming convention of

F<MNEMONIC>.<APPLICATION>

 The company mnemonic is part of the file name because if each

lead company has its own file, we must be able to tell which branch
each file belongs to
Example: FBNK.ACCOUNT

Slide 16
INT Files

 INT type applications

 These applications are implementation specific

 They do not belong to any company and there is only one file
irrespective of the number of companies in the installation

 All companies (Lead and Branch) can access these applications

 These applications follow the naming convention

F.<APPLICATION>

 The company mnemonic is NOT part of the file name since there
will be only one file
Example: F.SPF, F.DATES, F.COMPANY

Slide 17
Two scenarios

 Lets consider 2 scenarios

 Installation of T24 spanning different countries
 Installation of T24 in one country

 Both installations have multiple branches

Slide 18
Installation with International Branches

 Banks that buy T24 can

have branches around
the world

 Different countries have

different local currencies

 So in this case, 8 Lead companies must be created during installation

 Each Lead Company will have their own set of FIN files
 We can have branch companies that shares these files

Slide 19
Installation with Local Branches

 In this installation of T24, all

branches will have the same
local currency

 There is no need to create

multiple Lead Companies

 One Lead company with multiple

Branch companies

 This type of set up is called Multi

Book set up

Slide 20
Accessing Files – INT File Options

Lead Company A INT Files are ALWAYS

Lead Company B
shared by all
Lead / Branch companies

Branch 1 Branch 2 Branch 1 Branch 2

T24 INT Files

Slide 21
Accessing Files – CUS File Option 1

CUS Files are shared

in most
Lead Company A Implementations, but can Lead Company B
be separate for
each Lead company

Branch 1 Branch 2 Branch 1 Branch 2

T24 INT Files T24 CUS Files

Slide 22
Accessing Files – CUS File Option 2

CUS Files are shared in

Lead Company A most Implementations, Lead Company B
but can be separate for
each Lead company

Branch 1 Branch 2
Branch 1 Branch 2

T24 CUS Files T24 CUS Files

T24 INT Files
Company A Company B

Slide 23
Accessing Files – FIN Files Option 1

Lead Companies have

there own FIN files
Lead Company A (normal setup) but Lead Lead Company B
Companies can
also share FIN Files

Branch 1 Branch 2 Branch 1 Branch 2

T24 FIN Files T24 FIN Files

T24 INT Files T24 CUS Files
Company A Company B

Slide 24
Accessing Files – FIN Files Option 2

Lead Companies have

Lead Company there own FIN files Lead Company
A (normal setup) but Lead B
Companies can
also share FIN Files

Branch 1 Branch 2 Branch 1 Branch 2

T24 CUS Files T24 INT Files T24 FIN Files

Slide 25
Summary

 There are three types of files in T24

 Live
 Unauthorized
 History
 We can create two types of companies in T24
 Lead Company
 Branch Company
 T24’s Applications are broadly divided into three main types
 CUS
 FIN
 INT

Slide 26
 Thank You !!!

Presented By:
Prakash Parupudi