GP1[1].Global Processing-R10.01.pdf

8/11/2019 GP1[1].Global Processing-R10.01.pdf

http://slidepdf.com/reader/full/gp11global-processing-r1001pdf 1/38

Welcome to the “Global Processing Part – I” learning unit. In this learning unit you will learn

GEN4-T24 Directory Structure and Application Classification-R08.02

ow pro uct w a ow n epen ent ose o us ness process ng or certa n companeswhilst other companies continue to process online transactions in one T24 installation. This

mode of operation is particularly suitable to implementations where a single T24environment is used in multiple geographical locations. The time difference means that it

would not be possible to run a single Close of Business process.



After completion of this learning unit, you will be able to,

•Understand the need for Global Processing Product

•Explain Multi-Company and Multi-Book set up in T24

•Describe main features of GP

•Understand amended file layout for GP




Companies are categorized as Master / Lead Company and Branch Company

Master Company / Lead Company

This is the first company (normally BNK), set up in T24 with a complete set of data tables

It will be present in all types of T24 environment

Store all financial level data in its own set of tables

More than one Lead Company can exist in a T24 environment

Branch Company

Its financial level data will be shared with a Lead Company

A branch should be linked to a Lead Company

No other Company could be linked to a Branch Company

A Branch in addition will always share its local currency and Batch holiday table with theLead Company.







In a Multi Company environment, application level COB batches will be separate for each

ea ompany,

In this example there are 3 Lead Companies US0030303, JP0040404, CH0040505

Example : The Lead Companies USG, JPN, SWL will have their own Batch records :

USG/AC.REPORTS, JPN/AC.REPORTS, SWL/AC.REPORTS

These batches will be separately processed



In a Multi-Company setup in an GP environment,

You can run COB for an individual company or for a group of companies. In this example

there three lead companies US0030303, JP0040404, CH0040505. Notice that two leadcompanies JP0040404 and CH0040505 are in the same group 004 (digit 3-5) and one lead

company US0030303 are in 003 group. While executing COB in an GP environment youcan run for two companies which are in the same group or for an individual company in thesame group. How? You will learn as you go along.

Independent COB processing can take place using the GLOBAL PROCESSING (GP)

product

Different local currencies can be set up for Lead Companies

If the bank operates over a large geographical area with different time zones, and a separateCOB processing is required for the Companies using the GP functionality.

Example: Two offices of a bank one in CH (Switzerland) with local currency CHF andanother in USA with local currency USD each setup as a Lead Company.



If there is only one Lead Company with multiple Branch Companies, the T24


nsta at on s ca e a u t oo etup.

All Branches will share the files of the Lead Company and will not have their ownfiles at database level.

All companies will share financial level data tables.The Lead Company BNK and its Branch Companies BR1 and BR2, will share the

file FBNK.ACCOUNT for the Account application.

Similary, they will share the file FBNK.MM.MONEY.MARKET for the Money Marketapplication.



In an installation of T24 in which the local currency is the same, then there is no need to

create erent ea compan es. owever, you nee you may a so create mu t p e eacompanies with the same currency.

When a bank has branches spread across different geographical locations with different

local currency for each country there must a different company setup. When a bank hasbranches located in the same country with the same local currency multi-book environmentwould suffice.




In a Multi Book environment, application level Close of Business (COB) batches for the

ranc es w e n e to t e r ea ompany

Example: For the LD application level Batch, there will be only one Batch record :MF1/LD.END.OF.DAY for the Lead Company: MF1 and its Branches: MF2 and MF3

The LD records of the Lead Company and its Branches will be processed in the same Batch

job



There is no need to have separate COB processing (Global Processing) for the Companies,

or examp e, w en t ey are n t e same t me zone

Example: All the offices in a bank in UK, with one office designated as a Lead Company andother Offices as Branch Companies attached to the Lead Company



Implementation in which both Multi Company and Multi Book type environments will


co-ex st.

Multiple Lead Companies with Branch Companies is referred to as an ExtendedMulti Company Setup.

INT files will be shared by all the Lead and Branch Companies. Example – F.COMPANY, F.SPF.

FIN files are Company specific. Example – FUSG.ACCOUNT, FJPN.ACCOUNT,FSWL.ACCOUNT.

CUS files can be Company specific or can be shared. Example – FUSG.CUSTOMER only or FUSG.CUSTOMER, FJPN.CUSTOMER and

FSWL.CUSTOMER



Banks that implement T24 can have branches around the world. Different countries have

erent oca currenc es. n suc a case n you s ou create at east one eacompany for each local currency in T24.




In an Extended Multi Company environment, application level COB batches will be separate

or eac ea ompany

Example : The Lead Companies USG and JPN, will have their own Batch records :USG/LD.END.OF.DAY and JPN/LD.END.OF.DAY

These batches will be separately processed.

In a Multi Book environment, application level Close of Business (COB) batches for the

Branches will be linked to their Lead Company

Example: For the LD application level Batch, there will be only one Batch recod :

USG/LD.END.OF.DAY for the Lead Company: USG and its Branches: CR1 and CR2

The LD records of the Lead Company and its Branches will be processed in the same Batch job



If a bank operates in different countries with different local currencies. Each country will be

set up w t a ea ompany an ts own ranc es

Possible for the Lead Companies to share the same Customer file, but have different localcurrencies and currency table.

Each country can run its own COB (using Global Processing)




In any installation of T24 when you run COB it gets executed for all companies by default

t at means n a on – nv ronment t e process ng or a compan es ta es p ace atthe same time on a common system calendar. This implies that the common calendar

must ensure that a working day in one country must be a working day for all companies.

Each company must share a common LOCAL.COUNTRY or LOCAL.REGION table. Thisimplies that a shared system calendar is used for the bank’s processing, even though theactual financial entities may exist in different countries



In a GP Environment

The ability to allow COB processes to run at different times for companies or groups of

companies requires the system to allow each company to use a different system calendar,since different countries will have different holidays.

Look at the example above, there are 3 lead companies in different region that is

US0010001 (New York) which is in North America, GB0010002 (London) which is in Europeregion, JP0010003 (Japan) is in Asia region.

If you would like to run COB at different times for these companies or group of companiessystem should allow each company to use different a different calendar since each country

follow different holiday table.

How would you cater to this situation?



The Global Processing product allows independent operation of companies within a T24

envronment. e pro uct w a ow n epen ent c ose o us ness process ng orcompanies whilst other companies continue to process online transactions.

This mode of operation is particularly suitable to implementations where a single T24

environment is used in multiple geographical locations. The time difference means that itwould not be possible to run a single close of business process.



Backup of System

At the end of the online processing the system is switched offline and a backup (either tapeor disk) is made of the entire T24 database. At this point the system is unavailable to allusers for entry of transactions.

COB processing, Error Management and Recovery

The end of day process is run by the BATCH.CONTROL application. Each job run duringthis process is not subject to transaction management and therefore no general recoveryprocedure for the failure of an individual process.

In the event of machine failure the system must be restored from the backup taken at thestart of the end of day process and the batch process re-run.

A software failure due to unexpected conditions will generate a FATAL error from theprocess. This will stop the batch process from continuing (there are a few exceptions wherethe process will continue and be treated as an exception event allowing the batch tocontinue). In this situation the batch can continue with manual intervention, although due tothe fact there in transaction management in the end of day process it is not possible toguarantee the integrity of the data in this case. The only way of guaranteeing the integrity ofthe data would be to restore the backup taken at the start of the batch and re-run the end ofday, this implies that the problem which caused the error will be resolved first – for most

banks this is not a practical option, the batch is set to continue with a manual correction andthe data is corrected during the next day.

On completion of the batch process another backup is usually taken. The system is thenswitched to online mode and all online transactions are subject to the standard T24transaction management. Under T24 transaction management the integrity of the data isguaranteed in the event of software or hardware failure.



Many large banks wish to use the multi-company functionality provided by the system, and

w s to mp ement n mu t p e s tes. s s current y poss e an wor s w t n a s m argeographical area, as COB processing can be run at a common time when the system can

be offline.

However in different geographical regions the need to take the system offline to run the endof day process means that finding the time to do this is either a very small window, or doesnot actually exist. In order to provide this ability the concept of Global Processing has been

introduced. Essentially this is the ability to manage many financial entities (Multi-Company)in a single T24 database, and allow each financial entity to work independently of date

restrictions.

In this learning unit you will learn the functionality changes required to allow processing ofdifferent entities COB processing. The requirement is to allow the running of the COB

processes for an entity or group of entities independently from one another.





In a Multi-Company setup, whether independent COB processing can take place using the

pro uct

YES

In a Multi-Book setup, that is for the Companies within the same Lead Company structurewhether independent COB processing can take place using the Global Processing (GP) ?

NO





BALANCE.INTERCOMP

Indicates in a multi company system that multi company processing will take place.

This basically allows financial level data to be stored in a separate table for each company.

YES indicates a Multi Company environment whereas YES in the BALANCE.INTERDEPT

field indicates that a Multi Branch environment is set up.

Validation Rules

Allowed Values are YES and NO. Mandatory input. Default Value of NO. No Change Field.



BALANCE.INTERDEPT

Indicates in a multi branch system that multi branch (or multi-book) processing will take

place.

This basically allows financial level data to be stored in the same database table for allcompanies, as opposed to Multi Company where the data is stored in a separate table for

each company.YES indicates a multi branch environment whereas YES in the BALANCE.INTERCOMPfield indicates that a Multi Company environment is set up.

Validation Rules

Allowed Values are YES and NO. Mandatory input. Default Value of NO. No Change Field.



Multi-Company

T24 supports the processing and production of financial balanced books from separate

financial entities within the same database. Each entity (COMPANY) maintains it’s owntransaction base, and can share common static information such as Customers, Currency

definitions. Companies may reside in different locations and have different local currencies.This is configurable upon creation of the COMPANY.

Each company must share a common LOCAL.COUNTRY or LOCAL.REGION table. Thisimplies that a shared system calendar is used for the bank’s processing, even though the

actual financial entities may exist in different countries. As a result the system may have alocal holiday defined as a working day, and an ‘empty’ processing day will exist for that

entity.

The system supports full inter-company accounting and will raise the correct inter-companyaccounting entries when transactions involving accounts or P&L in different companies is

used in a transaction.





The requirements for using Global Processing in the T24 system is listed below

1. GP product license to be received from Temenos.

2. Configuration for Traditional or Online Backup facilities.

3. Multi-Company Setup to be configured in T24.



The SPF application has to be updated with the GP product code. The field

. as to e mar e as ‘ .





Similarly, COMPANY application has been amended to incorporate GP with T24. Notice the

e s . , . , . , . neeto be setup accordingly.



Fields BRANCH.HOLIDAY, BATCH.HOLIDAY XX.BRANCH.CLOSED need to setup you

are go ng to earn t ese e s n eta as you procee urt er.



COMPANY.GROUP and RE.EXTRACT.PARAMS are amended accordingly.



Application VERSION and VERSION.CONTROL has new field added BUSINESS.DAY

w c ea s w t o a rocess pro uct.



(1) In a Multi-Book setup independent COB processing using the Global Processing (GP)

product is not possible.

a. True

b. False

(2) In a Multi-Co. setup independent COB processing using the Global Processing (GP)product is not possible.

a. True

b. False

(3) Application VERSION and VERSION.CONTROL has new field added which deals withGlobal Process (GP) product.

a.NORMAL

b.RESTRICTEDc. BUSINESS.DAY

d. CLOSED

(4) To operate in a GP mode and allow the use of independent Close of Business you must

set the GLOBAL.PROCESS flag to Y in.

a. DATES

b. COMPANY

c. SPF

d. HOLIDAY




In this learning unit/course, you learnt to,

•Understand the need for Global Processing Product

•Explain Multi-Company and Multi-Book set up in T24

•Describe main features of GP

•Understand amended file layout for GP



http://slidepdf.com/reader/full/gp11global-processing-r1001pdf 37/38GEN4-T24 Directory Structure and Application Classification-R08.02



Documents

GP1[1].Global Processing-R10.01.pdf