1. Welcome to the “OVERRIDE PROCESSING” learning unit.

This learning unit will

enable you to understand the concept and implement OVERRIDE PROCESSING in
T24.

GEN10.Override Processing In T24 1

 After completing this learning unit/course, you will be able to:

 Describe and differentiate types of overrides in T24

 Explain the applications used for Override Processing
 Setup up multi level restrictions on Override access

GEN10.Override Processing In T24 2

 An override in T24 is required in a situation where the user needs to be warned that he
has to confirm the action which he would be performing.
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. Now if you input the transaction to debit $100, when
committing it T24 must warn you about the insufficient funds available. T24 cannot
stop you, but it can warn you. T24 generates an override to do this. You will have only
two options, to accept it and complete the transaction or reject it and stop.

GEN10.Override Processing In T24 3

 1.When you input a record in any Application in T24 and commit it, it is possible that
you come across two types of messages.
1.1 Error Messages: Such type of messages are displayed -
Due to data not being input in mandatory fields
Due to incorrect data input
Due to incorrect relationship between field name and the data that is input.
In case of Error Messages, you need to correct the data input in the particular fields
and commit the transaction again.
A record is not saved till all errors are corrected. You cannot even put the record on
hold.

1.2 Override Messages: These are warning messages, at least most of the time. A
user may accept or reject override. If accepted, T24 saves the record and the override
message is stored as part of it in the field OVERRIDE. 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.

GEN10.Override Processing In T24 4

 1. ‘Override’ is the name of the field which stores the override messages generated
on committing the record.
1.1 This field is part of almost all the applications in T24.
1.2 It is a no input field and updated by T24.
1.5 Old overrides are deleted and the new ones are updated here

GEN10.Override Processing In T24 5

 1.There can be two different types of override messages. They are Non Blocked and
Blocked overrides.

1.1 A record which generates non blocked overrides can be authorised by any user in
T24.

1.2 A record which generates blocked overrides can be authorised only by users with
appropriate privileges. If you do not have sufficient privileges the record will go to
INAO (Input Not Approved due to Override) status.

By default, all overrides in T24 are Non Blocked in nature.

GEN10.Override Processing In T24 6

 Where are Override messages stored?
In the OVERRIDE Application. T24 applications generate override messages stored
here.
ID : ID of the record can be any meaningful alphanumeric string

GB Message : This field contains the actual override message that is displayed on
committing the record.

So are override messages only static text messages? What if they need to hold values
from the transaction? In that case, the override message will also contain a special
character ‘&’ and each ‘&’ is then replaced with a value when T24 actually generates
the override.

In the override ACCT.UNAUTH.OD, the first & is used to denote Currency, the second
& to denote Amount and the third & to denote Account number.

Type, Channel and Approve Method : These fields are used only in ARC IB and are
not in the scope of this learning unit. However, to give you little information about
Channel field, based on the type of Channel you select to access T24 (like call center,
branch, internet, etc.,), you can set this Override message to act differently such as a
warning message, an error message, a confirmation message, etc.,.

GEN10.Override Processing In T24 7

 Now what if we decide to change an override message in T24?

Prev Message : This field in the OVERRIDE application holds the message which was
previously displayed for that particular Override. Only overrides that have changed
over the years will have a value in this field.

Numeric Id : This is a no input field. T24 generates a unique number for every record
in the OVERRIDE application on committing the record. This number is prefixed with
‘O’ which resembles Override.

App Version: This determines which Versions or Applications will perform automatic
Override validation during an OFS process.

Subroutine: It applies when OFS is being used. If validation is required then the
highest priority will be given to a user defined subroutine and no further validation will
be performed.

Validation: Any added validation checks to be performed during an incoming OFS

message can be done here.

GEN10.Override Processing In T24 8

 You will now see an illustration to prove that all overrides in T24 by default are non-
blocked. In other words, no special permission is required to accept it.

For the Funds transfer transaction, the override message ACCT.UNAUTH.OD is

generated. On accepting the override, the transaction is committed. This record can
be authorized by any user as it is a non-blocked override.

GEN10.Override Processing In T24 9

 1. Now that you realise what a non-blocked override is, the next thing to learn is how
to block an override.
2. Any user can accept blocked overrides when generated and commit the record thus
moving it into INAU status.
3.To block an override in other words is to restrict access to particular users when it
comes to authorising a record with this override.
4. If the record which has generated blocked overrides is accepted by the user with
appropriate permissions, then the record becomes live or else it will move to INAO
status.

GEN10.Override Processing In T24 10

 You will now learn with the help of an illustration how to block an override in T24.

GEN10.Override Processing In T24 11

 To grant privilege to authorise records that have generated blocked overrides, you
must use the OVERRIDE.CLASS field in the USER application or EB.USER.ROLES
depending on whether Roles are set up or not. This field accepts any string data. The
relationship of this data entered here and the override is clearly visible from the screen
shots.

The override record has been modified to include the user class details thus making it
a blocked override.

The user AUTHUSER1 and any user belonging to the ACCOUNT.OFFICER role can
now authorise the record which generated the ACCT.UNAUTH.OD override.

You will now learn more uses of the fields APPLICATION and CLASS in the
OVERRIDE application.

Application : Specify a * to denote, irrespective of the application from which this

override is generated, only users with Class TRG in their User profile can accept the
override.
You can also specify Class Application wise. For example, if the Override is generated
in the FUNDS.TRANSFER application, then only users with Class TEM in their User
profiles can accept it.

Class : This field specifies a group name. Users belonging to this group alone will be
able to approve this override. Class name can be any descriptive text. Maximum of
four characters only. The group name specified in this field should be attached in the
User profiles in the field ‘Override Class’.

GEN10.Override Processing In T24 12

 Note that the user RELMGR is not attached to the class TRG.

Now login as the user RELMGR and input an FT transaction, accept the overrides and
commit the record. Open it in SEE mode and see the field Override.3 being suffixed
with *TEM which implies that only a user belonging to the class TEM can authorize the
record.

GEN10.Override Processing In T24 13

 Note that the user FO.EXEC is not attached to the class TRG.

Now login as FRONT OFFICE EXECUTIVE and authorize the record. You will see the
message ‘YOU CANNOT APPROVE ALL OVERRIDES’. This is because, the user
who tried to authorize the record is not one among the class specified in OVERRIDE
application.

You can see the record status has gone to INAO. Only users with the field Override
class set to ‘TEM’ in the user profile can authorize the record.

GEN10.Override Processing In T24 14

 Note that the user AUTHUSER is attached to the class TEM and TRG.

Now login as AUTHUSER and authorize the same FT record. Open the record in SEE
mode and check for the field Override.1 being suffixed with ‘*TEM*AUTHUSER’

TEM is the Class name.

AUTHUSER is the user who has approved the override.

Note that the field Authorizer still holds the user FO.EXEC and does not change to
AUTHUSER .

GEN10.Override Processing In T24 15

 If an user of the class TEM has input the FT transaction, Can any user authorize the
FT record?

Note that user FO.EXEC is not attached to the class TEM. Now can this user authorize
the record?

YES. Since the FT record was input by the user belonging to the class TEM, now any
other user who does not belong to the class TEM can authorize the record.

GEN10.Override Processing In T24 16

 1. There might be many such cases in a Bank that a simple Class restrictions may
not be sufficient.
2. What if there is a need to restrict access to authorize the record which has a
specific value?
Using an illustration you will learn how to block overrides based on conditions.

GEN10.Override Processing In T24 17

 1.When an unauthorized overdraft override message is generated in T24, only the
following users should be able to approve the override based on the following
conditions.
2. Account Officer classification
Table Row 1 : Only the user ACCTOFF1 can approve the override if the currency is
USD and the overdraft amount is in the range one to 10000
Table Row 2 : Only the user ACCTOFF2 can approve the override if the currency is
USD and the overdraft amount is in the range one to 10000
3. Manager classification
Table Row 1 : Only the user MANAGER1 can approve the override if the currency is
USD and the overdraft amount is in the range 10001 to 50000
Table Row 2 : Only the user MANAGER2 can approve the override if the currency is
USD and the overdraft amount is in the range 10001 to 50000
4. GM classification
Table Row 1 : Only the user GENMGR1 can approve the override if the overdraft
amount is in the range 50001 to 1000000

GEN10.Override Processing In T24 18

 To set the multiple level restrictions to approve an override you have to use the
application OVERRIDE.CLASS.DETAILS. You can set different groups who can
approve overrides only if the conditions specified in their groups are satisfied.

Data Def : This field refers to the & values in the override message.
ACCT.UNAUTH.OD is the Override in which &1 refers to Currency, &2 refers to
Amount and &3 refers to Account. In this example, conditions are specific to only
Currency and Amount and hence only &1 and &2 are defined. A user defined routine
can also be attached in the field DATA.DEF. User can write his/her own conditions to
be checked in the routine and depending on the result various classifications can be
set to approve the override. The routine name should be prefixed with the sign @ in
the field.

The fields from Classification to Data.To form a multi value set. The fields from
Data.Def.No to Data.To form a sub value set.

Classification : This field holds any user defined text that best defines the group
classification.

Data Def No. : This field indicates which data item, as defined in the field DATA DEF is
to be used for the classification.
The number in this field identifies which multi-value from the field DATA DEF is to be
referred. For example, the number '1' indicates that it is the data item defined by field

GEN10.Override Processing In T24 19

 DATA DEF.1 and the number '2' indicates that it is the content of field DATA DEF.2 . You can
also define one DATA DEF and use it for all the classifications.

GEN10.Override Processing In T24 19

 Comparison : It refers the operand to be used. Must select the valid operand you
would want to use for comparison. This field can be left without any input also.
Different operands available are
EQ which resembles Equal To , GE resembles Greater than or Equal To,
GT resembles Greater than, LE resembles Lesser thank or Equal To,
LT resembles Lesser than, NE resembles Not Equal To,
LK resembles Like, NR resembles Out of range,
RG resembles the range, UL resembles Unlike.

Data From : This field holds the value indicated in the field DATA DEF (according to
the field DATA DEF NO), is compared against the value in this field according to the
operator in the field COMPARISON. If the outcome of the comparison is true, the
corresponding CLASSIFICATION group will be allocated the override.

DATA.TO : This field holds the end value of a range.

GEN10.Override Processing In T24 20

 When the override message is raised from the application FUNDS.TRANSFER, the
conditions specified in the record TRAINING in the OVERRIDE.CLASS.DETAILS
application will be checked and appropriately validated.
If the override message is raised for an amount which is beyond the amount specified
in OVERRIDE.CLASS.DETAILS then only the users who belong to the class TEM can
approve the override.
When the override message is generated for applications other than
FUNDS.TRANSFER (denoted using a *), users with the field Override Class set to
TEM in their user profiles will be able to approve the override.

GEN10.Override Processing In T24 21

 Specify the value given in the field CLASSIFICATION (first multi value set) in
OVERRIDE.CLASS.DETAILS and in the field OVERRIDE CLASS in the User profiles
of ACCTOFF1 and ACCTOFF2.

Specify the value given in the field CLASSIFICATION (second multi value set) in
OVERRIDE.CLASS.DETAILS and in the field OVERRIDE CLASS in the User profiles
of MANAGER1 and MANAGER2.

Specify the value given in the field CLASSIFICATION (third multi value set) in
OVERRIDE.CLASS.DETAILS and in the field OVERRIDE CLASS in the User profiles
of GENMGR1.

GEN10.Override Processing In T24 22

 1. Login to T24 as any user and input a FT debiting an account with nil balance with
USD 9000.
1.1 Login as ACCTOFF1/ACCTOFF2 and authorise the FT.

GEN10.Override Processing In T24 23

 1.Login as any user and input an FT debiting an account with nil balance with
USD 10400.
1.1 Login as ACCTOFF1/ACCTOFF2 and authorise the FT.
1.2 Note that the record status is INAO as ACCTOFF1 does not have the privileges to
authorise transactions with overdraft amount beyond USD 9000.
1.3 Login as MANAGER1 and authorise the record.
1.4 The authoriser field will still show value of ACCTOFF1 only as initially the record
was authorised by the user ACCTOFF1.

GEN10.Override Processing In T24 24

 1.Login as any user and input a FT debiting an account with nil balance with USD
51000
1.1If ACCTOFF1/ACCTOFF2/MANAGER1/MANAGER2 login and try to authorize the
record, the record will go to INAO status.
1.2Only user GENMGR1 will be able to approve the override and authorize the record.

GEN10.Override Processing In T24 25

 1.Login as any user and input an FT debiting an account with nil balance with
USD 2000000.
1.1Note that the Override message is suffixed with *TRG. (Provided TRG is specified
in the CLASS field for FUNDS.TRANSFER)
1.2Since the overdraft amount does not fall into any of the ranges defined in the
OVERRIDE.CLASS.DETAILS application, the default class TRG defined for FT has
been used.
1.3Therefore, this override can be approved only by users who have class set to TRG
in their User profile.

GEN10.Override Processing In T24 26

 T24 always checks for conditions in the order specified in the
OVERRIDE.CLASS.DETAILS record.
For example, If an FT is input and the overdraft amount is 9000, the override message
will always appear as
<Override Message>* ACOF
A user with MGR override class set will not be able to approve the above mentioned
override.
When an override is to be approved T24 checks to see if the override class mentioned
in the user profile matches the override class suffixed with the override message. If
yes, approval is possible, else record will got to INAO status.

GEN10.Override Processing In T24 27

 Logically a user with MGR override class set should be able to approve an override of
9000 USD. To get this done, you need to add ‘ACOF’ apart from the ‘MGR’ class in
the user profile of MANAGER1 and MANAGER2.

GEN10.Override Processing In T24 28

 1.Amend the ACCT.UNAUTH.OD override to allow only the following users to approve
the override.
2.Create the necessary users
3.Default class to be used is TRG
4.Two trainees to form a group
The first group needs to create a record in OVERRIDE.CLASS.DETAILS application.
The ID should be TEMENOS.TRG. The first group to create the record and add in
details appropriate to GRP1. Once done, GRP2 needs to edit the record
‘TEMENOS.TRG’ and input appropriate details. Then, record passes on to GRP3 and
so on. GRP10 to link the OVERRIDE.CLASS.DETAILS record to OVERRIDE
application.
All groups will then have to create new accounts and input FTs debiting the account
and check override processing.

GEN10.Override Processing In T24 29

 You are now familiar with the concept of override processing in T24. Can an override
message be triggered as an error in T24?
The answer is yes. The field TYPE in OVERRIDE application has the following options
– Error, Auto, Message and Warning. When TYPE is set to Error, the override
message becomes an error. When TYPE is set to Auto, the override message will be
automatically accepted by T24 , the user acceptance is not required.

GEN10.Override Processing In T24 30

 You will not be allowed to commit the record when an error is raised in T24.

GEN10.Override Processing In T24 31

 In the previous example, the override was displayed as an error message. Now can
you define Channel specific error messages for overrides?

In the example shown ACCT.UNAUTH.OD is just an override. Only when the

CHANNEL of the transaction is INTERNET, this override should be displayed as an
ERROR. When defining as an error for a particular channel either an existing
EB.ERROR can be mapped as shown Or Customized message change be provided.

Note: - Channel should be configured in OFS.SOURCE record.

GEN10.Override Processing In T24 32

 1. Can you simply create a new Override without any hassels?
2. No. OVERRIDE is one of the core applications in T24. It is not possible to simply
create a new record in OVERRIDE application and let it to populate for any records in
any applications. Only TEMENOS DEVELOPMENT can do it. However Client
customization is possible but is not as simple as creating any record in OVERRIDE
application. All the override messages to be generated should be defined in the
OVERRIDE application in T24.

For example, when T24 wishes to raise an override stating that a particular account
has been over drawn, it will only say that an override ACCT.UNAUTH.OD needs to be
raised. T24 core then picks up the actual message from the field GB Message in
OVERRIDE application and displays it.

GEN10.Override Processing In T24 33

 Have you ever wondered why do you get a “SECURITY VIOLATION” message? What
is the reason you are getting it? what does that message actually mean?
If yes, your answers will be answered in the coming slides.

GEN10.Override Processing In T24 34

 1. EB.ERROR is the application where the error messages are stored in T24.
2. Record Id in this application is comprised of two parts:
2.1. The PRODUCT code. Ex: EB for core
2.2. Part 2: An abbreviated description of the error message. Ex: Security.violation

3. ERROR.MSG - Multi-language field contains the message that will be displayed in

the event of an application triggering this error.
4. CHANNEL - Used to define channel specific messages. Every OFS.SOURCE
record can be set to a specific channel. If there is a channel specified, the channel
specific message will be displayed as an error.
5. NUMERIC.ID – The corresponding error code for the error message.

GEN10.Override Processing In T24 35

 1. EB-SECURITY.VIOLATION record contains the error message that gets triggered
when:
1.1. invalid username/password is entered in the login page.
1.2. a user tries to open an application or use a function that he/she is not entitled to
(Application & Function level SMS restrictions).
2. Change the content of ERROR.MSG field’s first multi-value to “Invalid
Username/Password! Or not enough rights!” as shown in the screenshot on the right.

GEN10.Override Processing In T24 36

 1. Now try to enter either a invalid username/password in the T24 login page.

You will get the new customized error message, as shown in this slide!

GEN10.Override Processing In T24 37

 Now we will test if this error message is displayed when a user tries to open an
application or use a function that he/she is not entitled to (Application & Function level
SMS restrictions).

1. Create a user profile as shown in this slide.

2. Login using the user created and try to open the CUSTOMER application in Input
mode.

GEN10.Override Processing In T24 38

 1. EB-SECURITY.VIOLATION.2 record contains the error message that gets triggered
when:
1.1. a user tries to open a record in an application that contains data (field level) that
he/she is not entitled to view (Field level SMS restrictions).

GEN10.Override Processing In T24 39

 Now login using the newly created user and try to open a record in ACCOUNT
application with @ID 14087 (EUR account).

You will get the new customized error message as shown in this slide. This is because
the new user doesn’t have rights to open a record in ACCOUNT application which has
a currency not equal to USD.

Here the User profile is configured for multiple company restrictions.

1. First restriction is where the user can access all companies and all applications,
but can use the functions as ‘History Exception List Print See’.
2. Secord restriction is where the user can access all companies and in the
ACCOUNT application he can use the functions ‘Input Copy Delete’ with only
those accounts where the currency is USD.

GEN10.Override Processing In T24 40

 1. EB-SECURITY.VIOLATION.4 record contains the error message that gets triggered
when:
1.1. a user tries to query about records that contains data (field level) that he/she is not
entitled to view (Field level SMS restrictions).
2. Change the content of ERROR.MSG field’s first multi-value to “Sorry, you don’t
have permissions to query this data!”.

GEN10.Override Processing In T24 41

 1. Now try to open a record in ACCOUNT application with @ID equal to 61492 (JPY
account).

You will get the new customized error message as shown in this slide!

GEN10.Override Processing In T24 42

 1. OF-SECURITY.VIOLATION record contains the error message that gets triggered
when:
1.1. A user tries to perform any action in his/her session when the session is no longer
active (Except web server session timeout).
2. Change the content of ERROR.MSG field’s first multi-value to “Sorry, your session
is no longer active.”

GEN10.Override Processing In T24 43

GEN10.Override Processing In T24 44
 In this learning unit/course, you learnt about the Override Processing in T24

You will now be able to

 Describe and differentiate types of overrides
 Explain the applications used for Override Processing
 Setup up multi level restrictions on Override access

GEN10.Override Processing In T24 45