FILE STRUCTURE IN T24

Data entered into T24 applications are stored in files at the database level.
At the database level, these files are broadly classified into
1. Live files,
2. Unauthorized files
3. History files
4. Deleted History
5. SIM files.

Live files store only authorized records.

The field RECORD.STATUS will be BLANK for records in Live files.

Unauthorized files ($NAU) store unauthorized records.

There are various Record Statuses that can be associated with records in Unauthorized
Files. The Record Statuses are: INAU, INAO, INA2, RNAU, RNA2, RNAO, HNAU, IHLD
.
History files ($HIS) store old copies of authorized records.
When an authorized record is edited and the changes approved, the latest version of the
record is stored in the Live file and the old version is moved to the History file.
The History file can store any number of amendments of a particular record.

Deleted History($DEL)
Holds deleted unauthorized records.
Live files can never be deleted

Simulation -$SIM files store records that are generated after simulation.
These records are generated by T24 and hence there will be no audit fields for records in this
file

***************************************************************************

FUNCTIONS IN T24

‘ A’ is a function which allows the user to authorize a record.

'D' is a function that allows the user to delete a record that has not yet been authorized.
authorized record cannot be deleted.

'E' function allows the user to list the unauthorized records.

I function allows the user to input a record in an application.

L function is used to list live records

S allows user to only view the records.

‘R’ authorized records cannot be deleted. To remove an authorized record, the function is
R
esreveR

'H' a reversed record can be brought back using the History restore function

‘ Q’ audit Not available by default

V (Verify) is a special function. Applicable only for some applications.

AUDIT FIELDS:
1. RECORD.STATUS
Informaton about the status of the record is it unauthorized, is it authorized,
is stored in a field called RECORD.STATUS

2.CURR.NO
Is an audit field that indicates how many times the record has been
authorized/modified

************************************************************************
ENQUIRIES

When do we need enquiries?

Case1-When a bank manager wants to view all FUNDS.TRANSFER transactions where
the debit amount is greater than 10,000 dollars.

Case 2 - When a bank employee needs the account balance to handle customer queries.

ENQUIRY?
An enquiry is a query that is executed to fetch data from the database and display the
results in a user defined format. All enquiries in T24 are catalogued in ENQUIRY
application. Used to generate user defined reports

The ENQUIRY application is used to create/format the enquiry.

Enquiries are launched using the ENQ command followed by the name of the
enquiry
***********************************************************************

VERSIONS

Versions can be compared to the concept of 'Views' in Database Management systems.

Versions help us in creating screens with the fields we want.
Customized screens that display required fields from the application.
Improve the look and feel of the system.

A table may consist of several columns (fields) that might not be required for all.
users.
So the users can create views, consisting of the columns that they need account to.
requirement

All versions are catalogued in the VERSION application.

The ID of a VERSION is APPLICATION, VERSION.NAME

CUSTOMER

***********************************************************************
API
An API (Application Programming Interface) is a defined interface through which one
Software application talks to another software application.
Programs and devices can communicate safely, without knowing the internal workings.
that allow the other to function.
APIs make application developers' and product planners' jobs easier, working like ready
made building blocks for creating software.

API is just a middleman who handles your request and translates it into something the other
party can understand, without you having to really know what the other party’s systems and
data looks like in detail.

T24 functionality in VERSION and ENQUIRY is exposed through defined

APIs
Integrations that used to take many months or years can be accomplished in mere
hours because the exchange of data is regulated and standardized by the API provider
EXAMPLE OF API:
Postman
Postman is currently one of the most popular tools used in API testing.
***********************************************************************
COMMIT

When a record is committed, Overrides may be raised. Overrides are warning messages.
Override is a warning message generated to inform the Inputer 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 the transaction is input to debit $100, upon 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.

OVERRIDES
When a record is committed, Overrides may be raised. Overrides are warning messages. An
Override is a warning message generated to inform the Inputer 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
The account should be $100. When a transaction is input to debit $100, upon committing it to 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 of 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.

*****************************************************************************
SERVICES IN T24
 Need for Services

Banks have thousands of customers who have thousands of accounts. The bank has to
calculate interest for each account. Records older than 6 months must be archived
Currency exchange rates must be updated periodically to be applied in foreign currency.
transactions. Such work has to be done automatically without any user intervention

WHAT ARE SERVICES

Services are programs that run as background processes without user interaction.
intervention.

They can be scheduled or triggered by a manual activity.

They spawn multiple processes and are centrally monitored by Core Banking.

EXAMPLE OF SERVICEMultithreading.
They help automate processes and tasks.
They are catalogued in the TSA.SERVICE application.
Viewing a record from TSA.SERVICE

*********************************************************************
RETAIL BANKING
The AA module provides a flexible framework that allows a number of new T24 modules to be
created. The application provides a business component based architecture for the
management of products. Arrangements are the part of the Retail Banking suite of products.
TELLER
Teller incorporates the administration of Tills, processing of local and foreign currency.
transactions
updates, advice on production, automatic charge defaulting, rate defaulting and so on.

TELLER.FINANCIAL.SERVICES (TFS) is a T24 application, which facilitates capture of

information for all these transactions in one screen and with one click, and creates a
Consolidated Entry (parameterized) on the Customer account, a Consolidated Charge
and a Consolidated Transaction Advice.
 Role Description

Cashier Assists the Bank customers with an array of monetary transactions

Head Teller Supervises and coordinates the activities of the Tellers in the
Branch and approves transactions

Payments Officer Process transactions which involve Inward and Outward

Remittances, Clears Operations and Cheque Collection

Payments Authorizes remittances, clears and cheque collection transactions

Supervisor and ensure adequate controls and risk processes are followed

Branch Operations Oversees all data processing activities supporting account and
Manager deposit servicing functions of a bank

*****************************************************************************
LIMITS
Credit limits are held by customer and by product.
In the simplest case, a LIMIT might be held for one product with an individual customer.
For example: we might decide to limit placements with ABC Bank to no more than 50M
USD. If we were to attempt to input a placement, which meant that this LIMIT would be
exceeded then, an override would be required at deal input.
The LIMIT application uses the following parameter files and these have to be set up before
limits can be used and be applied at either Customer or Liability level. These parameters are
used to define the structure of limits.
For secured LimitsLIMIT.PARAMETER and LIMIT.REFERENCE records must be
entered
For unsecured Limits parameter tables for COLLATERAL application are also
required to be set up as they are used to indicate how the limit is secured.
LIMIT.PARAMETER
LIMIT.REFERENCE
Commodity Limits
 Country Limits
Currency Limits

1. LIMIT.PARAMETER
Within this file are defined parameters that determine the way in which the LIMIT system
operates. Only one record with an id of SYSTEM is required.
LIMIT.PARAMETER controls the following:
A 'number of days' to define how many days prior to LIMIT Expiry Date
and Review Date the approach of these events is to be reported.
A date and cycle to indicate when the first revaluation occurs and at
what frequency thereafter.
A date and cycle to indicate when the Commodity, Country and
Currency reports must be produced.
2. LIMIT.REFERENCE
This table defines various parameters and links contracts and accounts to LIMIT.REFERENCE.
The key to this table is the product, defining the product hierarchy which is the second
dimension to Limits.