Local Fields – R15 G-1

Local Fields – R15 G-2

Local Fields – R15 G-3
Local Fields – R15 G-4
 T24 applications contain all the necessary fields to store data pertaining to an
application. Some banks may want to record additional information in an application.
These fields may not be applicable for other banks. So, what can the bank do? Can it
request Temenos to add some new fields to the application to store additional
information? Temenos might not do that, simply because not all banks need that
field. What is the solution? To cater to such situations, Temenos has introduced Local
Ref Fields which can be created in a particular client environment to meet their need
without affecting the actual application.

Local fields are user defined fields and are totally customisable by the bank.

Once these local fields are created, they can be reused in various applications in T24 .

Local Fields – R15 G-5

 To create a local field in T24, you will need two applications. LOCAL.TABLE and
LOCAL.REF.TABLE

The application LOCAL.TABLE is used to create the user defined field and set
properties of that field.

LOCAL.REF.TABLE is used to link the newly created field to any T24 application.

The process of creating the field is stand alone and therefore a field created can be
reused in any application in T24. You will learn how to create a local field and attach it
to a T24 application in the next few slides.

Local Fields – R15 G-6

 To create a local field in T24,. LOCAL.TABLE and LOCAL.REF.TABLE are used

The application LOCAL.TABLE is used to create the user defined field and set
properties of that field.

LOCAL.REF.TABLE is used to link the newly created field to any T24 application.

The process of creating the field is stand alone and therefore a field created can be
reused in any application in T24. You will learn how to create a local field and attach it
to a T24 application in the next few slides.

Local Fields – R15 G-7

Local Fields – R15 G-8
 You will now learn to create a local field. The ID of a record in this application was
numeric until R09 but from R10 it need not be numeric.

The field DESCRIPTION holds the description of the field.

SHORT.NAME field will hold the actual name of the field that you want to create.
The value given in this field will appear in the application you will attach this field to.

MAXIMUM.CHAR and MINIMUM.CHAR fields are used to denote the maximum and
minimum number of characters the local field can hold. If a value is defined in
MINIMUM.CHAR field, then the local field becomes a mandatory field.

The field CHAR.TYPE holds the information about what type of data can be input in
the local field created.

If you want to define the list of values that can be stored in this field, then you can
enter possible values in the field VETTING.TABLE which can be multi valued to store
multiple values.

REMARK field is used to store the enrichment for the value in the VETTING.TABLE
field.

Local Fields – R15 G-9

 Now you are ready with the local field created which needs to be attached to an
application. LOCAL.REF.TABLE is used to link the local field to an application. The ID of
a record is the application to which you want to attach the local field.
The ID of LOCAL.TABLE created is attached to the field LOCAL.TABLE.NO

SUB.ASSOC.CODE field is used to denote whether this local field is a multi value field
or a part of associated multi value set. Possible values in this field are as follows.
XX. denotes that this is a single Multi Value field.
XX< denotes the start of an associated multi value set.
XX- denotes that this is part of an associated multi value set.
XX> denotes the end of the associated multi value set.
If nothing is mentioned in this field, then it is a normal field in an application.

Note that you cannot change the order of local fields. If you try to add a new local
field in between the existing local fields, you will not be able to commit the record.
Also, a local field once created cannot be deleted. Therefore care should be taken
before deciding to create one local field.

Local Fields – R15 G-10

 All the fields that appear on an application will have an entry in the
STANDARD.SELECTION record for that particular application. So then, do you have to
edit the SS record to add this local field that you have created just now? No. On
authorising a record in the LOCAL.REF.TABLE, the corresponding record in SS
application will get updated with the relevant data. Take a look at the CUSTOMER
record in SS application which is populated with the new field that is created.

Note that the field USR.TYPE is set to ‘I’ which denotes that this is an I-descriptor field
and is not stored with this name in the database. The physical field LOCAL.REF has
been multi-valued to hold the data of the newly created field. Note that this is the
fourth local field created for this application which is denoted as LOCAL.REF<1,4> in
the field USR.FIELD.NO.

The field USR.VAL.PROG contains the name of the IN2 routine that needs to be
invoked to perform data type validation. For this specific field the routine IN2A will be
invoked as you have set the field CHAR.TYPE to ‘A’ in LOCAL.TABLE application.
The other fields denote the display format and whether it is a single or multi value
field and if it is a language specific field.
You are done with creating the local field. So now, you should be able to see the local
field in the respective application. You have created a local field VALUED.CUSTOMER
and attached it to the CUSTOMER application. Open a new or an existing CUSTOMER
record, and you should be able to see the local field created with all the features that
you have set in the LOCAL.TABLE and LOCAL.REF.TABLE applications. Note that the
local field will be populated even in already existing records in this application and

Local Fields – R15 G-11

 not only in the new records. All the local fields will appear towards the end of the record before the
audit fields and in the order as they are created.
Note the enrichment being displayed as defined in the LOCAL.TABLE application.

Local Fields – R15 G-11

Local Fields – R15 G-12
Local Fields – R15 G-13
 1. True
2. True
3. True
4. False
5. Local field is part of an associated multi value set

Local Fields – R15 G-14

Local Fields – R15 G-15