Welcome to Versions for Multi Book Setup learning unit.

This learning unit will

enable you to learn the importance of versions in multi-book environment

Versions for Multi Book Setup-R10.01

The conventions used in this learning unit are,

1. Applications in T24 are represented in bold uppercase letters.
2. The fields in the applications are mentioned in uppercase letters.
3. This learning unit is example based. First an example output will be shown then
you will be taught the steps to create the Version. At the end of each section a
workshop is given to test your level of understanding.

Versions for Multi Book Setup-R10.01

At the end of this learning unit you will be able to,

1.

Analyse the importance of versions in multi-book setup

2.

Explain the processing of BUSINESS.DAY field in version

3.

Analyse the importance of AUTO.COMP.CHANGE and

COMPANY.ACCESS fields in version

4.

Access records without actually logging into the company

Versions for Multi Book Setup-R10.01

This task teaches you about restricting access to versions based on certain criteria.
The requirement for the task is as follows,
1. A version ACCOUNT,OPEN is created in the multi-company set up
2. The users of the branch company MF.BRANCH1 should be allowed to access the
version only on a NORMAL working day

Versions for Multi Book Setup-R10.01

You will restrict the users of the branch to access the version only on a normal working
day. Now to ensure this set the current day as closed day for the branch company.
Where will you specify this for the MF1 Branch? The closed date will be specified in
the company record of the branch.
The records of COMPANY application is used to define the companys name ,
mnemonic and other default parameters that are required for a company. You are now
required to define the closed date for the company.
In the company record set the field BRANCH.CLOSED to the current date. Now you
have set today as the closed day for the MF1 branch. Once you modify your company
record for the branch, the closed date modification should be reflected in the DATES
application. Now you will check the DATES application .

Versions for Multi Book Setup-R10.01

1. Here you can see the record in the DATES application for the LEAD company.
The CURRENT.DAY field indicates the type of business day for a particular
company. Is the current day set to CLOSED for the LEAD company ? No, because
today is set as closed day only for the MF1 branch (GB0010003) and not for the
LEAD company. This you can see in the field CURRENT.DAY.
2. For the branch you can see that the field CURRENT.DAY is set to CLOSED. Note
today is 16 DEC 2009 as specified in the field TODAY.

Versions for Multi Book Setup-R10.01

In the version record you can specify on what type of days the version should be
executed.
BUSINESS.DAY This field is based on the CURRENT.DAY field of the DATES
application.
By setting the field BUSINESS.DAY to NORMAL you tell the system that this particular
version can be executed only on official working days. Thereby you restrict the access
of the version on closed days of the branch company. The other options for the field
BUSINESS.DAY are CLOSED & RESTRICTED.
CLOSED The CLOSED option indicates that the version can be executed on all days
in the company.
RESTRICTED The RESTRICTED option indicates that the that the version can be
run on a normal or on restricted working days .
After you amend the version authorise it.

Versions for Multi Book Setup-R10.01

Now in order check the given task login to the MF1 branch (KNOWLEDGE GROUP
MF2) using the tools icon in the browser.

Versions for Multi Book Setup-R10.01

Execute the version ACCOUNT,OPEN from the command line. The T24 system
displays an error message saying that the version cannot be executed on closed days
of the branch.

Versions for Multi Book Setup-R10.01

1. Create a version for the ACCOUNT application with the following fields @ID,
CATEGORY, CURRENCY, CUSTOMER and ACCOUNT.TITLE.1

2. Users of the LEAD company should have access to the version on all days
3. Users of the branch company MF.BRANCH1 should be allowed to access the
version only on a normal working day

Versions for Multi Book Setup-R10.01

10

This task aims at teaching you the importance of COMPANY.ACCESS field in version.
The requirement for the task is as follows,
In a multi-company set up have you tried executing the same version from different
companies? You can very well execute a version from a different company. Now can
you restrict other company users from accessing a particular version created for a
specific company in T24.

1. A version ACCOUNT,TRG1 has been created for the ACCOUNT application in the
company GB0010001
2. Allow only users of the company GB0010001 to execute this version. Specify the
restriction in the version record

Versions for Multi Book Setup-R10.01

11

The version ACCOUNT,TRG1 is created in the company GB0010001.In the version,

set the field COMPANY.ACCESS to OWN. By doing this you restrict the users of
different companies from executing your version .

Versions for Multi Book Setup-R10.01

12

You can execute the version from the GB0010001 (BNK) company.

Versions for Multi Book Setup-R10.01

13

Now log into a different company by using the tools icon. T24 displays an error
message when a user executes the version from a different company.

Versions for Multi Book Setup-R10.01

14

This task teaches you to access a record of the branch company from the LEAD
company. To access a record you are not going to actually log into the branch. The
requirement is stated here,

1. Create a version based on the ACCOUNT application with the given fields
CUSTOMER,MNEMONIC, CURRENCY,
CATEGORY, ACCOUNT.TITLE,
RECORD.STATUS, CURR.NO, INPUTTER, AUTHORISER and OVERRIDE

2. The user logged into the LEAD company should be able to access account
records of the branch company also

Versions for Multi Book Setup-R10.01

15

Create the version with all the specified fields. Using the version , the user logged into
the LEAD company should be able to access account records of branch companies.
You will allow the user to do so by using the field AUTO.COMP.CHANGE in the
version.
AUTO.COMP.CHANGE This field is used to access the other company records
without actually logging into it. This works only for a multi-branch set up. Set this field
to YES in your version record.

Versions for Multi Book Setup-R10.01

16

1. An account record is being created in the branch company MF2, using the version
ACCOUNT,TRG (Temenos Training).
2. Login to the Lead company MF1, and you will be able to view the record using the
same version.

Versions for Multi Book Setup-R10.01

17

1. Create a version based on the ACCOUNT application

2. The user logged into the LEAD company should be able to access account records
of the MF2 Branch company also

Versions for Multi Book Setup-R10.01

18

1. True
2. True
3. True
4. False

Versions for Multi Book Setup-R10.01

19

1. The BUSINESS.DAY field of the version is used to restrict access to the version
based on the type of business day
2. A version can be executed on all official working days of a bank when the field
BUSINESS.DAY is set to NORMAL
3. The RESTRICTED option of the BUSINESS.DAY field indicates that the that the
version can be run on a normal or on restricted working days
4. The CLOSED option of the BUSINESS.DAY field indicates that the version can be
run on all working days of the bank

Versions for Multi Book Setup-R10.01

20

1. In the version when you set the field COMPANY.ACCESS to OWN, you restrict
the users of different companies from executing your version
2. Records can be accessed from different companies in a multi-book setup using a
version
3. To access records of another company without actually logging into it, the field
AUTO.COMP.CHANGE should be set to YES in the version

Versions for Multi Book Setup-R10.01

21

In this learning unit you have learnt the importance of versions in multi-book
environment. You will now be able to,
1.

Analyse the importance of versions in multi-book setup

2.

Explain the processing of BUSINESS.DAY field in version

3.

Analyse the importance of AUTO.COMP.CHANGE and

COMPANY.ACCESS fields in version

4.

Access records without actually logging into the company

Versions for Multi Book Setup-R10.01

22

Versions for Multi Book Setup-R10.01

23

Versions for Multi Book Setup-R10.01

24