Local Reference Fields in T24
Date Of Issue Version Changes By Reviewed
By
Dec 2004 1.0 Initial Alagammai
Palaniappan
1.1 Changes Sara Cleur
Information in this document is subject to change without notice.
No part of this document may be reproduced or transmitted in any form or by any means,
electronic or mechanical, for any purpose, without the express written permission of TEMENOS Holdings NV.
Local Reference
Table of Content
Table of Content ................................................................................................................................... 2
Introduction........................................................................................................................................... 3
Tables Involved In Creating A Local Reference Field ........................................................................... 3
LOCAL.TABLE .................................................................................................................................. 3
LOCAL.REF.TABLE .......................................................................................................................... 3
Illustration.......................................................................................................................................... 3
Creating Local Reference Fields With Conditions ................................................................................. 3
Illustration.......................................................................................................................................... 3
Additional Information ........................................................................................................................... 3
Summary .............................................................................................................................................. 3
Temenos Training Publications Page 2 of 11 December 2004
T2ITT – R05 – 1.0
Local Reference
Introduction
Temenos T24 is a global banking software that caters to various banking needs all over the world. It
has a great number of applications that cater to the various needs of banks. Each application contains
a large number of fields to store information for the bank, but it is not possible for an application to
contain every possible field that a bank may require. To overcome this, T24 provides us with the
functionality of ‘Local Reference’ fields. These are fields that can be added to applications depending
on the banks requirements. They are totally customisable.
For instance, a bank wishes to store the passport number of a customer along with the rest of the
customer information. In the Customer application there is no field to hold the passport number. How
do we overcome this problem? What we could do is, create a local reference field and attach it to the
customer application. Problem solved.
Tables Involved In Creating A Local Reference Field
There are 2 applications namely
• LOCAL.TABLE : Used to define the field - the name and attributes
• LOCAL.REF.TABLE : Application that is used to link the local field to a particular application.
LOCAL.TABLE
This application is used to define a local reference field.
ID : Numeric
Field Description
GB Description Holds the general description of the local
reference field.
GB Short Name Holds the display name of the local reference
field.
Maximum Char Maximum number of characters that the field can
hold.
Minimum Char Minimum number of characters that a field can
hold. If this field is set to contain any value, then
the field becomes a mandatory field.
Char Type Specifies the type of data the field can hold.
A – Alphanumeric
AA
AAA
ANY
D – Date
DD
R
S
SS
SSS
Temenos Training Publications Page 3 of 11 December 2004
T2ITT – R05 – 1.0
Local Reference
TIME
TIMES – Time in seconds
TIMEH – Time in hours
TIMEHS – Time in hours and seconds
AMTLCCY
AMTCCY
TEXT
FQU - Frequency
Vetting Table Used to define a user defined list box of valid
values. Multi value this field and specify the
values that should be allowed for the field.
GB Remark Contains the enrichment for the values defined in
the field ‘Vetting Table’
LOCAL.REF.TABLE
This application is used to link the local reference defined using the LOCAL.TABLE application with
T24 applications.
ID : T24 Application Name to which the local reference field is to be attached to
Field Description
Local Table No Local reference field number as defined in the
LOCAL.TABLE application
Sub Assoc Code Specifies if the local reference field is a multi
value field or a part of an associated multi value
set.
XX. : Multi value field
XX< : Start of an associated multi value
set
XX- : Part of an associated multi value
set
XX> : End of an associated multi value
set
Illustration
We need to create a local reference field with the name ‘VALUED.CUSTOMER’ and attach it to the
Customer application. This can contain either a value ‘YES’ or ‘NO’.
Let us create the local reference field using the LOCAL.TABLE application.
Temenos Training Publications Page 4 of 11 December 2004
T2ITT – R05 – 1.0
Local Reference
Now let us attach the local reference field to the CUSTOMER application.
The customer application with the new local reference field:
Temenos Training Publications Page 5 of 11 December 2004
T2ITT – R05 – 1.0
Local Reference
The local reference field that we just created can be attached to any number of applications in T24. All
that we need to do is to specify the ID of the LOCAL.TABLE application in the LOCAL.REF.TABLE
record of the respective application.
Creating Local Reference Fields With Conditions
We have just seen how to create a simple local reference field. We can input the value YES or NO in it.
But we can also create fields that are automatically defaulted and remain as NO INPUT fields. Let us
see how to do this with the help of an example.
Illustration
The bank wants to segregate their customers into groups. One group will be called ‘Valued
Customers’. These are customers whose account category is 1001 (Current account) and their sector
is 1000 (Financial Corporations). The other group is ‘Normal Customers’. These are customers who
don’t fall into the above category.
For this reason the bank wishes to include the local reference filed that we just created –
VALUED.CUSTOMER to the Account application. When added to the Account application, depending
on the value of the ‘Category’ and ‘Sector’, the Valued Customer field should be automatically
populated. The bank wishes to have this field as a no input field.
If Category = 1001 and SECTOR = 1000 then, VALUED.CUSTOMER field should contain a value
YES. Else should contain a value NO .
Let us understand a few more fields in the LOCAL.TABLE application that will enable us to specify
conditions for local reference fields.
Field Description
Application Name of the application where the local reference
field has been/is to be attached
Decis Field Field name in the application specified in the
‘Application’ field whose value needs to be
checked
Replace File Specifies an external file, the value of whose
fields will be checked for matching conditions to
Temenos Training Publications Page 6 of 11 December 2004
T2ITT – R05 – 1.0
Local Reference
provide a default local reference or for verifying
user Input.
Replace Field Specifies the field(s) from an external file whose
value will be checked to provide a default or to
verify a user input local reference.
Decision Specifies the standard decision formats used to
check for matching/non-matching values in either
DECIS FIELD or REPLACE FLD.
The value of the field in either DECIS FIELD or
REPLACE FIELD will be checked according to
this decision
'EQ', 'GE', 'GT', 'LE', 'LK', 'LT', 'NE', or 'UL'.
Input not allowed if there has been no input in
DECIS FIELD.
Decision Fr Specifies the value of a decision or the start of a
range. The value in this field is the start of a
range when DECISION is 'EQ' or the only value
required for DECISION 'EQ', 'GE', 'GT', 'LE', 'LK',
'LT', 'NE', or 'UL'.
Must be input if DECISION is defined.
Decision To Specifies the end of a decision range.
The value in this field represents the end of a
decision range.
Override possible Specifies whether input in this local reference can
differ from the decision rules.
If input is 'Y' then the user may input a local
reference that does not meet the decision criteria
in this table. The system will prefix the enrichment
with "OV!" and prompt the inputter for an override.
If the input is blank then the value must meet the
decision criteria.
Default Possible Specifies whether the system should default the
value in VETTING TABLE.
If the input is 'Y' the system will provide the input
for the user at validation according to the decision
criteria.
If the field is left blank then the user must input a
matching value in the local reference field.
Noinput Change Fld Indicates whether the local reference field can be
input by the user or amended by the user.
The local reference field can be set as 'NOINPUT'
ie. the system will provide input, or 'NOCHANGE'
where the user cannot amend the field after
authorisation.
Application Vet Identifies the Application against the key of which
the input to this field is to be Validated, unless
actual values of input allowed have been
Temenos Training Publications Page 7 of 11 December 2004
T2ITT – R05 – 1.0
Local Reference
specified in Field 6, VETTING TABLE.
This field is used to identify the Application
against the key of which the input to this field is to
be validated.
Appl Enrichm Field Indicates which field of the Application defined in
Field 18 (APPLICATION VET) is to be used for on
line enrichment when an Application Vet has
been specified.
Now let us modify the local reference field that we have created to accommodate the condition that we
discussed earlier.
Field is going to be attached to ACCOUNT
CUSTOMER field in ACCOUNT is link to
CUSTOMER file from where the SECTOR value
is picked up and checked as first condition
Second condition is the CATEGORY field in
ACCOUNT.
Let us attach it to the ‘Account’ application.
Let us input a record in the Account application and commit the record.
Temenos Training Publications Page 8 of 11 December 2004
T2ITT – R05 – 1.0
Local Reference
The local reference field is defaulted to NO. This has happened because the conditions mentioned in
the LOCAL.TABLE have not been satisfied.
Sector should be 1000 and Category should be 1001
From the screen shot below we can see that one of the conditions have not been satisfied. Thus the
field was defaulted to NO.
Temenos Training Publications Page 9 of 11 December 2004
T2ITT – R05 – 1.0
Local Reference
Additional Information
As mentioned earlier, if we wish to store specific information and if appropriate fields are not available
in T24, then we can create local reference fields. We need to understand that once we decide on the
structure of a table (Application in case of T24), we cannot keep adding and deleting fields, as it will
affect the data in it. This being the case how can we create local reference fields? Wont they alter the
structure of the application? What happens to the existing data?
Whenever an application is created, a field by name ‘LOCAL.REF’ is created. This is always created
as a multi value field. When we wish to store extra information (information other than what can be
stored in the set of fields given by T24), all that we need to do is to multi value this field and specify a
different name for the multi value. When we attach a local reference field to an application using
LOCAL.REF.TABLE, we actually multi value the physical ‘LOCAL.REF’ field and specify a different
name for the multi value.
We cannot change the order of the local reference fields once they are added to a particular
application. The damage has been explained above. Local reference fields cannot be removed too.
That makes it essential to plan if we really require the extra fields in the applications.
The screen shot is of the CUSTOMER applications local reference fields
Now if I try to add a local reference field with ID 666 in the middle
Temenos Training Publications Page 10 of 11 December 2004
T2ITT – R05 – 1.0
Local Reference
Summary
• Local Reference fields are created in the LOCAL.TABLE application (ID is numeric) and are
attached to the applications using LOCAL.REF.TABLE (ID is the application name)
• The order of the local reference fields cannot be changed in an application once they are
added
• The same local reference field can be reused in any number of applications
• Values for a local reference field can be a predefined list set as a vetting table or else they can
ordinary fields that can be input
• Special conditions can be set and values can be defaulted in the local reference field,
NOINPUT and NOCHANGE property can be set
Temenos Training Publications Page 11 of 11 December 2004
T2ITT – R05 – 1.0
