DW.

EXPORT - User Guide

Release R15.000
June 2015

©2015 Temenos Headquarters SA - all rights reserved.

Warning: This document is protected by copyright law and international treaties. Unauthorised reproduction of this document, or any portion of it, may
result in severe and criminal penalties, and will be prosecuted to the maximum extent possible under law.
Table of Contents
Introduction 3
Purpose of this Guide 3
Intended Audience 3
Application Overview 4
Installation Guide 5
Pre-Installation 5
Identifying Main GL and PL Reports 5
Post-Installation 5
Data Extract 6
Data exported from T24 into Insight /Insight Risk 13
DW EXPORT records to be configured for Insight 17
Additional DW EXPORT tables in Temenos Insight 18
DW EXPORT records to be configured for Insight Risk 20
Configuration and Creation of CRB files 21
Mode of Extraction 25
Online Extraction TSA.SERVICE record 25
COB Extraction 25
DW Export API Records 27
Other Records 27
Automated tool to configure DW Export utility 29
Prerequisites 29
MERGE.COMPANY in DW.EXPORT 31
Parallel Extraction in DW.EXPORT 32
Configure DW.EXPORT 32
Configure BATCH 33
Configure BATCH.NEW.COMPANY 34
FAQs 37

DW.EXPORT - Release R15.000 - Page 2 of 40

Introduction

Purpose of this Guide

The DW.EXPORT application is a standard interface between T24 and BI products (Insight and Insight Risk products) which extracts data
from T24 in comma separated value (CSV) text files. This DW Export utility is released as part of DW product available in T24 and it can be
used to export information out of T24. The application contains all configurations to extract data for TEMENOS Insight and Insight Risk prod-
ucts. The entire data extraction process can be run as part of T24 system COB or through an online service.

The following sections in this document provide all the details about the installation (pre and post) processes of DW Export utility and the con-
figuration involved to extract data using DW.EXPORT application.

Intended Audience
This guide is intended for the use of generic users/business users who implement and use DW.EXPORT application.

DW.EXPORT - Release R15.000 - Page 3 of 40

Application Overview

DW.EXPORT is a T24 application which stores all the tables required and extracted for TEMENOS Insight and Insight Risk products. The files
that are going to be extracted as part of DW Export need to be stored as data records to ensure that further extractions do not require any com-
plex coding changes and can be managed using data records.

As part of post-installation setup, the user should perform the basic steps listed in the following sections for extracting the requisite data from
T24.

Currently the DW.EXPORT utility supports only UTF-16E format and stores the extracted files as .CSV files in the local directory with a delim-
iter “~” configured at lead company level. User can transfer the created files to another location.

DW.EXPORT - Release R15.000 - Page 4 of 40

Installation Guide

Pre-Installation
Setting up the System
The first prerequisite for DW Export utility is to install the DW product.

Note: User should get the DW license code from the Licensing team..

After the installation of DW product in SPF and COMPANY record, the T24.UPGRADE online service needs to be run to release base appli-
cations including DW.EXPORT, DW.EXPORT.PARAM and pre-configured standard DW.EXPORT records. These records are required for both
Insight and Insight Risk, and the related data records such as EB.API records for SELECT and PROCESS APIs, BATCH and TSA.SERVICE rec-
ords etc.,

Now, the latest update for DW_BiExport component should be downloaded from TCSP portal to get all the latest fixes related to the DW.E-
XPORT application. Install these updates using the T24.UPDATE service.

Ensure to authorise the following data records after installing the latest update.

l STANDARD SELECTION

l EB.ERROR

l EB.API

l TSA.WORKLOAD.PROFILE

l TSA.SERVICE

l BATCH

l DW.EXPORT

Identifying Main GL and PL Reports

The next pre-requisite is to identify main GL (General Ledger) and PL (Profit and Loss) reports that the Bank wants to see and use in the
Insight product. Before configuring DW EXPORT in the T24 system, this identification is required for Insight and not required for Insight Risk.

Post-Installation
Setting up DW.EXPORT
All T24 applications require a standard Insight system build. The Insight Risk product will be released in the DW.EXPORT application as part
of the installation of the DW package. They just need to be input and authorised. User needs to create and configure only one additional
extract, that is, CRB Extract Records for main GL and PL reports. The configuration process for the CRB extract is explained later in this doc-
ument.

DW.EXPORT - Release R15.000 - Page 5 of 40

Data Extract

The following two steps should be followed to configure the extract of a file in the data extract.

1. Individually open the default list of records released in DW.EXPORT in “INPUT” mode and then commit them. Replace the ‘SYSTEM
FIELD’ in FIELD.NAME with the actual field name and ensure that the TAKEOVER field is set as BULK for the required files.

2. Configure DW.EXPORT.PARAM for all the lead companies for which the extract needs to be run. The extract path for each lead com-
pany is setup separately to indicate where the CSV files should be generated and stored. The required DW.EXPORT records for the cur-
rent lead company should be input in FILE.NAME by multi-valuing or using the ‘ALL’ option. This will populate all the DW.EXPORT
records with TAKEOVER is not null. This record must be configured for each lead company.

The following screen shot illustrates the configuration of a company level record and the required fields to be configured in the record. In a
multi-book environment, this record needs to be created and configured only at the lead company level.

As illustrated in the example, the path name where the file needs to be extracted should be specified on the field FILE.PATHNAME, and it
must be entered for all the T24 files that are going to be extracted for the current company in FILE.NAME by multi-valuing it.

Optionally, the user can specify a transfer routine in the field TRANSFER.RTN to transfer the CSV files into Insight/Insight Risk Server in
binary mode. There is sample transfer routine DW.TRANSFER.ROUTINE that has been released along with the DW Export utility. Using the
sample as a guide, the user can write their own ftp transfer routine.

The following screen shot illustrates the LIMIT record:

DW.EXPORT - Release R15.000 - Page 6 of 40

The user can specify APIs to modify or add data during extraction. This is required when the data extraction needs these routines to perform
data extraction from linked files. These are pre-configured for the standard BI files which are released along with the DW package.

The following are steps involved in CATEG.ENTRY and ACCT.ACTIVITY extractions (these procedures are required only for Insight).

CATEG.ENTRY Extract
For Monthly Extract

1. Input DW.CATEG.ENTRY.SELECT.API in SELECTION.RTN

2. Type the year and the month (format: YYYYMM) in the YEAR.MONTH field with current year and month.
3. Ensure that TAKEOVER field is set as BULK
For Daily Extract:

After the first successful data extraction, all subsequent extracts are carried out daily using the above monthly extract setup. Following are the
settings for daily extraction.

1. SELECTION.RTN field value should be removed.

2. TAKEOVER field value should be changed from "BULK" to "DAILY".
3. YEAR.MONTH field value should be removed.

ACCT.ACTIVITY Extract
By default, the ACCT.ACTIVITY file will be extracted every month. If the extract for ACCT.ACTIVITY file needs to be performed for a specific
month, then enter the specific year and month (YYYYMM) in the YEAR.MONTH field.

Starting from the R11 release, T24 supports the following extraction types:

1. Daily Extract
2. Incremental Extract
3. Bulk Extract
4. Online Extract
The first three extracts are considered as offline extracts and the last one is considered as an online/real time extract.

Daily Extract
Daily Extract is the customized selection for T24 tables. If a file needs to be extracted as DAILY, then it is based on the CONCAT file defined in
EXTRACT.FILE in DW.EXPORT. Selection will automatically be done based on EXTRACT.FILE, but user should have PROCESS API to han-
dle this properly.

For example, STMT.ENTRY, RE.CONSOL.SPEC.ENTRY and CATEG.ENTRY files can be extracted through the DAILY extract.

DW.EXPORT - Release R15.000 - Page 7 of 40

The below screen shot shows how DAILY Extract can be configured for the STMT.ENTRY file

Incremental Extract
The Incremental extract is used to extract the records that were amended or updated in the previous day or newly introduced in the specific
T24 file. To do this type of extract, set the TAKEOVER field to INCREMENTAL in the DW.EXPORT record. This is mainly used to improve
the performance of extracting from T24 and importing into Insight for Banks with huge volumes of data. For example, the CUSTOMER file
could be extracted as incremental. For the incremental extract, the field INCR.KEY.FIELD is mandatory and must be a valid unique field from
CUSTOMER table.

DW.EXPORT - Release R15.000 - Page 8 of 40

The below screen shot shows how INCREMENTAL Extract can be configured for the CUSTOMER.file.

Bulk Extract
The Bulk Extract will extract all the records from a T24 table. For the initial extract, all the DW records will be configured as BULK in the
TAKEOVER field.

The exceptions are STMT.ENTRY and RE.CONSOL.SPEC.ENTRY. These files will always be DAILY; ACCT.ACTIVITY will only be extracted
monthly using the YEAR.MONTH field. CATEG.ENTRY will initially extract the entire month and then from the next day onwards, it will be a
DAILY extract.

DW.EXPORT - Release R15.000 - Page 9 of 40

The below screen shot shows how BULK Extract can be configured for the DATES file

Online Extract
The Online extract is also called the Real Time extract. It will capture the transactions that are configured for online extract, and directly update
the target database on the Insight server for those real time transactions once they are authorised inT24.

There is an online auto service for the online extract. It will be run in phantom mode to pick up those online transactions. To do this type of
extract, the TAKEOVER field should be set as ONLINE.

For example, STMT.ENTRY and ACCOUNT file to capture the real time account movements with transaction codes etc.

DW.EXPORT - Release R15.000 - Page 10 of 40

Configurations for real time extract

To enable real time and continuous extract, old ETL can be used to do few configurations and external .jar files can be used to upload into exter-
nal database. Refer Data Warehousing user guide to setup CLASSPATH for the jar files in .profile or remote.cmd and ensure to set up con-
nection properties in dwUtils.properties as below.

1. The ENABLE field should be set to NO in DW.EXTRACT.PARAM for the SYSTEM record. This enables T24 to
switch off the legacy ETL Tool using DW.EXTRACT.

DW.EXPORT - Release R15.000 - Page 11 of 40

 2. DW.EXPORT must be enabled for capturing transactions in online by setting up DW.UPDATE.ONLINE in DW.E-
XPORT.PARAM for the SYSTEM record. This enables image capture of the transactions for both online and incre-
mental mode when set as BOTH.
3. Configure online target database at the company level as shown below:

4. Set TAKEOVER field and Online target table for the required files at DW.EXPORT level to upload the real time
transactions to the target database as shown below.

5. Start the DW.EXPORT.ONLINE service, which will upload the data into Insight Server directly.

CRB Extracts
CRB Extracts need to be configured by the bank in DW.EXPORT. The CRB report is a standard T24 GL reconciliation report. Refer “Con-
figuration and Creation of CRB files” section if the bank has not yet configured these as it is a pre-requisite to setup DW.EXPORT. For a given
CRB report, DW.EXPORT needs to be configured as follows:

DW.EXPORT - Release R15.000 - Page 12 of 40

 Note: Two CRB reports need to be configured for Insight – one is for the General Ledger and another one is for the
Profit and Loss report. Both should be included in DW.EXPORT. For example, MBGL is for GL Report and PMPL is for
P&L Report.

The SEL.COMPANY field needs to be specified with the lead company ID as it will be set up for other DW.EXPORT records.

Data exported from T24 into Insight /Insight Risk

The default list of records released in the DW.EXPORT application is listed below. The list will be extracted from T24 and it will be used in
Insight and Insight Risk products.

ID Extract Details

ACCOUNT This will extract interest and charges that have been collected from the cus-
tomer on the COB date. This record only needs to be set up, if consolidation
has been set up for CATEG.ENTRY records in job IC.COB otherwise the
CATEG.ENTRY records will extract this information.

ACCT.ACTIVITY Extract contains details of each Account for each month in which there has
been any Activity over the Account, used to calculate interest and charges,
Total Debit and Credit Turnover, Total number of entries with each different
Transaction Code processed, and the total value of the entries with each
Transaction Code. These details are held in the record for the month in
which the entries are processed, regardless of the Value Dates of the entries

ACCT.CAPITALISATION The purpose of this table is to specify the next date and subsequent
frequency of application of debit and credit interest for a specific Account

AM.VEH Valuation of portfolio at each month for last working day. Extract details
include information about Asset and Sub-Asset type.

CATEG.ENTRY Extract information will be used as a basis for P & L information, it con-
tains information such as Transaction Code, PL Category( Interest Income /
Expense / Fees etc.,), Account officer, Product Category, Amount in Local
currency, Customer ID etc.,

DW.EXPORT - Release R15.000 - Page 13 of 40

CATEGORY Extract information provides information about Category codes used to clas-
sify financial transactions on T24 according to the type of business oper-
ation or product.

The use of these codes together with personal Customer characteristics (for
example: Residence, Status, Industry and Sector codes etc.,) will enable the
bank to produce balance sheets and returns reflecting a co-ordinated and
structured view of its operation by directing business transactions to their
appropriate place on the report.

COLLATERAL This file is used to record the details of collateral submitted by a customer,
the value of collateral, and optionally, to link it directly to a customer's sup-
porting deal elsewhere in the system.

COLLATERAL.RIGHT The collateral right file is used to record the status of a right of security and
to indicate against which customer outstanding, the right applies.

COLLATERAL.TYPE This file is used to define classes of collateral object such as buildings,
stocks, guarantees (or subdivisions thereof).

COMPANY Extract information detail about the company level parameter setup which
includes information about various applications attached to the company,
Default Local Currency, Financial Year End, Holiday Details and the
Default currency rate conversion etc., This information is common for LEAD
and Branch company. A Branch company is linked to a Lead company and
uses the same data files as its Lead company with the exception of financial
reporting files.

COUNTRY Extract provides information on list of countries, Geographical block and

Currency Code

COUNTRY.GROUP Extract information provides information about List of countries attached

within that country group, used to know the profitability per country group
wise where the business being carried out and also used to determine the res-
idence or non-residence when applying charges.

CURRENCY Extract information includes information such as Number of decimals, Inter-

est Day Basis, Currency Market, Country Code etc.,

CURRENCY.MARKET Extract information provides list of currency market (for example: Cash Mar-
ket, Money Market, Bond Market etc.). The markets defined on this table are
used to identify the correct exchange and revaluation rates to be applied to
each Currency.

CUSTOMER Extract provides basic information about a customer such as Customer ID,
Mnemonic, Country, Nationality, Residence, Sector, Industry, Language,
Customer Liability, Account Officer etc.; Details in the Customer base record
are descriptive and not financial.

CUSTOMER.STATUS Extract information provides information about the customer based on the
internal rating that can be assigned to a customer in order to know the
credit worthiness of a customer (for example: AA, AA+ , B, BB+ etc.,)

DATES A Date record exists for each company. This record contains the run dates
for the previous, the current and the next working.

DW.EXPORT - Release R15.000 - Page 14 of 40

DEPT.ACCT.OFICER Extract provides information about the DAO, information like DAO code,
DEPT.LEVEL, DEPT.PARENT, Information is vital in order to arrive prof-
itability, Volume of business generated by each DAO and at DEPT LEVEL
can be customer / product

DEPT.LEVEL Extract provides information about the hierarchy of the organisation like
Board, Management, Divisional, etc.

EB.CONTRACT.BALANCES The EB.CONTRACT.BALANCES file records the information held in the

CENTRAL.REPORTING FILE '(CRF)' down at contract level. Account bal-
ances, principal outstanding amounts in product files and any related
amount fields such as interest reserves, accrued charges, commissions, etc.
held for each contract may be viewed into records held on the EB.CO-
NTRACT.BALANCES.

EB.RATING Extract provides external rating codes assigned by the External Rating
Agency, This helps to identify the external market credibility / performance
by the customer.

EB.RATING.AGENCY Extract provides list of external rating agencies and their codes.

GEOGRAPHIC.BLOCK Extract provides information about list of countries attached within that
Geographical Block.

GLOBAL.CUSTOMER Extract provides information about the customers belonging to a specific

group. For example: Citi Bank N.A, Citi Bank SG under CITI GROUP.

GROUP CAPITALISATION The purpose of this table is to specify the next date and subsequent
frequency of application of debit and credit interest for a group of Accounts.

INDUSTRY Extract provides list of industries and their codes. Information is useful
when we analyse the profitability / Exposure of a customer based upon the
industry.

INTEREST.BASIS Extract provides List of Interest Basis, forms the basis in calculating the
Interest.

LANGUAGE Extract provides list of languages used as a Multilanguage option in T24.

LIMIT The Limit System is designed to monitor the availability and utilisation of
Limits. Customer Limits are monitored in real-time. Back end reports are
used to monitor Limits for Commodities, Countries, Country Groups and
Currencies.

LIMIT.REFERENCE A Limit Reference is a numeric code which defines a type of Limit. For those
cases where it may be necessary to sub-divide a Limit Reference, a hierarchy
can be defined. A hierarchy can consist of up to three levels such as Global
Limit, Product Limit and Sub product Limit.

LIMIT.TXNS System will not extract all LIMIT.TXNS, but extract those LIMIT ids along
with contract information which is directly linked to COLLATERAL.RIGHT.

LN.ASSET.CLASS Provides information about the asset class such as Performing, Non-Per-
forming which is used as a basis to allocate provisions for the assets held in
the books

DW.EXPORT - Release R15.000 - Page 15 of 40

RE.CONSOL.SPEC.ENTRY Provides all the contracts movements, interest accruals and position reval-
uation entries etc., which will be used in Insight to build movement types
report.

RE.CRF.XXXX This is a CRB file extract where XXXX is T24 GENERAL LEDGER Report
name

RE.STAT.REP.LINE Information about the definition of the content of a report line. It also holds
the details for line narratives, sub headings, totalling for each report and
control of spacing (empty lines) before and after lines and totals

RELATION The Relation table is used to specify the various types of relation that could
exist between Customers. The purpose of identifying such relationship codes
is to provide the bank with the ability to "group" various clients together for
reporting or information purposes

SC.FUND.FLOW Extract information contains details of security and fund flow information.

SEC.ACC.MASTER This file contains information relating to a customer’s security account (port-
folio). Any number of portfolios may be opened for a given client, each
uniquely identified by a separate suffix.

SECTOR Provides list of Sector codes which can be assigned to each Customer record
to group them into broad classifications such as Private Sector, Public Sec-
tor, Corporate, Banks etc.

SECURITY.MASTER This file is used to record and maintain details of all securities opened
within the Securities module. Comprehensive information relating to each
Security, along with the conditions applicable to it, is stored in this file.

SECURITY.TRANS Security related information at an individual Transaction and portfolio

level.

SECURITY.POSITION This file provides information of security cash flows for Market Risk.

STMT.ENTRY The STMT.ENTRY file contains the debit and credit entries that are passed
over any accounts. And all the debit and credit entries raised as on Yes-
terday will be extracted used in Insight.

TARGET Target codes defined on this table are assigned to Customer records of T24
to indicate how the Customer fits in with the Bank's overall marketing
strategy. For example: HNI, Prime customer etc.,

TRANSACTION The Transaction Table contains information about all the Transaction Codes
which may be used within T24. The Transaction codes contain and identify
important processing conditions which will be defaulted by the Applications
if no other input has been entered at the transaction level.

Used in case of reference purpose, generating charge, assigning a unit cost

associated with each Transaction code. This will allow Customer and
Account profitability to be produced taking into account not only the earn-
ings detained from the Customer but also the cost included in providing the
services to customers

USER This file is used by the Security Management System to control who has
access to T24., when and to what information and facilities

DW.EXPORT - Release R15.000 - Page 16 of 40

DW EXPORT records to be configured for Insight
DW Export records to be configured for Insight are listed here. Using automated configuration tool, the below records will automatically be con-
figured which will then be extracted out of T24 as CSV files.

DW EXPORT Frequency Comments

ACCOUNT Monthly Optional, to be turned on only when the detail entries update of
netted CATEG.ENTRY is switched off.

ACCT.ACTIVITY Monthly YEAR.MONTH should be input by the user

ACCT.CAPITALISATION Daily

CATEG.ENTRY Monthly/Daily First time alone this file should be extracted with YEAR.MONTH of
current month along with select API and TAKEOVER as Y, from next
day onwards TAKE.OVER to be set as N and select API to be
removed

CATEGORY Daily

COMPANY Daily

COUNTRY Daily

COUNTRY.GROUP Daily

CURRENCY Daily

CURRENCY.MARKET Daily

CUSTOMER Daily

CUSTOMER.STATUS Daily

DATES Daily

DEPT.ACCT.OFFICER Daily

DEPT.LEVEL Daily

EB.RATING Daily

EB.RATING.AGENCY Daily

GEOGRAPHIC.BLOCK Daily

GLOBAL.CUSTOMER Daily

GROUP.CAPITALISATION Daily

INDUSTRY Daily

INTEREST.BASIS Daily

DW.EXPORT - Release R15.000 - Page 17 of 40

 LANGUAGE Daily

LIMIT Daily

LIMIT.REFERENCE Daily

LN.ASSET.CLASS Daily

RELATION Daily

RE.CONSOL.SPEC.ENTRY Daily

RE.STAT.REP.LINE Daily

SECTOR Daily

STMT.ENTRY Daily

TARGET Daily

TRANSACTION Daily

USER Daily

RE.CRF.XXGL Daily This record needs to be configured manually for master GL report in
T24 system, where XXGL is General Ledger report name (Man-
datory)

RE.CRF.XXPL Daily This record needs to be configured manually for master PL report in
T24 system, where XXPL is Profit and Loss report name (Optional)

Insight PWM

AM.VEH Daily Available for Insight PWM and to be turned ON this file only if AM
product is installed

SC.FUND.FLOW Daily Available for Insight PWM

SEC.ACC.MASTER Daily Available for Insight PWM

SECURITY.MASTER Daily Available for Insight PWM

SECURITY.TRANS Daily Available for Insight PWM

SC.POS.ASSET Daily Available for Insight PWM

Additional DW EXPORT tables in Temenos Insight

Apart from the standard list DW.EXPORT records, the user can configure the below T24 applications if the respective product such as BL, LD,
MM, MG, LD and FX is installed in T24 without select and process APIs and with SYSTEM FIELD.

DW EXPORT Product Frequency Comments

DW.EXPORT - Release R15.000 - Page 18 of 40

ACCOUNT.CLOSURE AC Daily

POSITION AC Daily

BL.BILL BL Daily

BL.REGISTER BL Daily

BL.TYPE BL Daily

CUST.DOCUMENT DM Daily

DE.ADDRESS DE Daily

DEALER.DESK FX Daily

FOREX FX Daily

ACCOUNT.CREDIT.INT IC Daily

ACCOUNT.DEBIT.INT IC Daily

LC.TYPES LC Daily

LETTER.OF.CREDIT LC Daily

DRAWINGS LC Daily

LD.LOANS.AND.DEPOSITS LD Daily

LMM.SCHEDULES LM Daily

MD.DEAL MD Daily

MG.MORTGAGE MG Daily

MM.MONEY.MARKET MM Daily

PD.BALANCES PD Daily

ENTITLEMENT SC Daily

SEC.TRADE SC Daily

ASSET.TYPE SC Daily

SUB.ASSET.TYPE SC Daily

ACCT.GEN.CONDITION ST Daily

BASIC.INTEREST ST Daily

FT.COMMISSION.TYPE ST Daily

PERIODIC.INTEREST ST Daily

STANDING.ORDER ST Daily

DW.EXPORT - Release R15.000 - Page 19 of 40

DW EXPORT records to be configured for Insight Risk
DW Export records that have to be configured for Insight Risk are listed in the following table. Using the automated configuration tool, the rec-
ords below will automatically be configured and extracted out of T24 as CSV files.

DW EXPORT Frequency Comments

DW EXPORT Frequency Extract Company DW EXPORT

COMPANY Daily Customer company level COMPANY

COUNTRY Daily Customer company level COUNTRY

COUNTRY.GROUP Daily Customer company level COUNTRY.GROUP

CURRENCY Daily Customer company level CURRENCY

CUSTOMER Daily Customer company level CUSTOMER

SECTOR Daily Customer company level SECTOR

Credit Risk

CATEGORY Daily Customer company level CATEGORY

COLLATERAL Daily Customer company level COLLATERAL

COLLATERAL.RIGHT Daily Customer company level COLLATERAL.RIGHT

COLLATERAL.TYPE Daily Customer company level COLLATERAL.TYPE

DW.GL.ACCOUNT.MAPPING Daily Lead company level DW.GL.ACCOUNT.MAPPING

EB.CONTRACT.BALANCES Daily Lead company level EB.CONTRACT.BALANCES

EB.RATING Daily Customer company level EB.RATING

EB.RATING.AGENCY Daily Customer company level EB.RATING.AGENCY

INDUSTRY Daily Customer company level INDUSTRY

LIMIT Daily Customer company level LIMIT

LIMIT.REFERENCE Daily Customer company level LIMIT.REFERENCE

LIMIT.TXNS Daily Customer company level LIMIT.TXNS

SC.POS.ASSET Daily (IR & Equity) Customer company level SC.POS.ASSET

SEC.ACC.MASTER Daily (IR & Equity) Lead company level SEC.ACC.MASTER

SECURITY.MASTER Daily (IR & Equity) Customer company level SECURITY.MASTER

SECURITY.POSITION Daily (IR & Equity) Customer company level SECURITY.POSITION

STOCK.EXCHANGE Daily (IR & Equity) Customer company level STOCK.EXCHANGE

DW.EXPORT - Release R15.000 - Page 20 of 40

 Market Risk

INTEREST.BASIS Daily Customer company level INTEREST.BASIS

PERIODIC.INTEREST Daily Customer company level PERIODIC.INTEREST

PRICE.TYPE Daily Customer company level PRICE.TYPE

SC.POS.ASSET Daily Customer company level SC.POS.ASSET

SC.PRICE.CHANGE Daily Customer company level SC.PRICE.CHANGE

SC.TRADING.POSITION Daily Lead company level SC.TRADING.POSITION

SEC.ACC.MASTER Daily Lead company level SEC.ACC.MASTER

SECURITY.MASTER Daily Customer company level SECURITY.MASTER

SECURITY.POSITION Daily Customer company level SECURITY.POSITION

STOCK.EXCHANGE Daily Customer company level STOCK.EXCHANGE

SUB.ASSET.TYPE Daily Customer company level SUB.ASSET.TYPE

Configuration and Creation of CRB files

This part of configuration and creation of CRB flat files are required only for the Insight product and not required for Insight Risk.

The Banks that have not configured the CRB flat files generation should follow the below steps to configure and create CRB flat files for the
CRB Extract:

l First, the Banks have to decide the GL and PL reports that need to be extracted as part of CRB extract for Insight.

l Whether the Bank wants to generate direct CSV files or CRB flat files (FXXX.RE.CRF.YYYY)Å and then CSV files
through the existing report job of RE.OUTPUT.EXTRACT. The RE.EXTRACT.PARAMS must be configured accord-
ingly for those reports.

Where XXX is the company mnemonic and YYYY is the standard T24 report available in RE.STAT.REPORT.HEAD
application.

l There are two new fields viz., CRB.FILE.LEVEL and CSV.FILE.FORMAT introduced in RE.EXTRACT.PARAMS appli-
cation to achieve this.
l There are two new fields viz., CRB.FILE.LEVEL and CSV.FILE.FORMAT introduced in RE.EXTRACT.PARAMS appli-
cation to achieve this.

DW.EXPORT - Release R15.000 - Page 21 of 40

l FIN level generation- Option 2: New option to generate the CRB flat files at Lead company level (FIN), the RE.E-
XTRACT.PARAMS must be defined as below with the new field CRB.FILE.LEVEL as ‘FIN’.

l Direct CSV files – Option 3: New option available from R11 to generate the CSV files directly from reporting job
instead of generating normal CRB flat files, and then generating the CSV files.

l Once the RE.EXTRACT.PARAMS is configured, then RE.RETURN.EXTRACT application must be configured as

below.

l After setting up the above two parameters, attach the RE.EXTRACT.FILE file record ID in the DATA field for the
job RE.OUTPUT.EXTRACT in the batch record of RE.PRINT.DEAL.RPT if CRB flat files are going to be generated
as part of COB and based on the setup RE.EXTRACT.PARAMS configured with either Option 1 or Option 2 as
above.

DW.EXPORT - Release R15.000 - Page 22 of 40

l If the CRB reports are going to be generated with reporting online service and the setup in RE.EXTRACT.PARAMS
is configured either with Option 1 and Option 2, then ensure that have specified all the report ids. For example:
MBGL in the batch record RE.RETURN.EXTRACT is for online service.

l To generate the CRB flat files online, start the service RE.RETURN.EXTRACT along with TSM records in TSA.SER-
VICE.

DW.EXPORT - Release R15.000 - Page 23 of 40

l If the Option 3 (Direct CSV) setup is chosen in RE.EXTRACT.PARAMS, enable the job RE.OUTPUT.EXTRACT as
Daily from Adhoc for those reports in the batch record as below
l If T24 data is going to be extracted as part COB, configure the DW batch record as below (Here for example
MBGL report is configured for Direct CSV files).

l If T24 data is going to be extracted as part of online service, configure the DW batch record as below (For exam-
ple MBGL report is configured for Direct CSV files).

DW.EXPORT - Release R15.000 - Page 24 of 40

Mode of Extraction

The actual data extraction process can be performed in two ways

1. Online Extraction
2. COB Extraction

Online Extraction TSA.SERVICE record

This can be performed using the standard T24 Services functionality. The TSA Service record DW.EXPORT.SERVICE will be released from the
core. This service record get released either as <XYZ>/DW.EXPORT.SERVICE or DW.EXPORT.SERVICE depending upon whether the set-up
is Multi company or not (where XYZ represents the lead company mnemonic).

Start the TSA.SERVICE record and also ensure that TSA.WORKLOAD.PROFIE is linked properly.

TSA.WORKLOAD.PROFILE

TSA.WORKLOAD.PROFILE record for this service must be created with as many agents as required, and linked to the TSA Service record
DW.EXPORT.SERVICE.

COB Extraction
The batch records <XYZ>/DW.EXPORT.DETAILS will be released as part of DW.EXPORT utility, where <XYZ> are the lead company mne-
monic to do extract as part of COB.

Ensure the frequency is set to Daily for the jobs DW.EXPORT.CLEAR and DW.EXPORT.INFO in DW.EXPORT.DETAILS as shown below
from Adhoc, so that the generation of CSV files will be run as part of COB, and then there will be no need to run DW.EXPORT.SERVICE.

DW.EXPORT - Release R15.000 - Page 25 of 40

DW.EXPORT - Release R15.000 - Page 26 of 40
DW Export API Records

In the DW.EXPORT application, two APIs can be attached. First API is SELECT API which is used to select the records with some selection
criteria if bank needs; second API is PROCESS API which is used to process the selected records one by one. These APIs should be defined in
EB.API record with SOURCE.TYPE as BASIC. These are provided with some sample API and examples as follows.

SELECT API
SUBROUTINE DW.XX.SELECT.API (FILE.NAME, R.DW.EXPORT, REC.LIST)

Incoming Parameters

FILE.NAME -The name of the file that is going to be extracted as CSV file through DW.EXPORT. For example: CATEG.ENTRY, RE.CRF.MBGL
(where MBGL is GL report head), CUSTOMER, etc.

R.DW.EXPORT - Holds the whole DW.EXPORT record (dynamic array) for the file in FILE.NAME.

Outgoing Parameters

REC.LIST -The selected record id list, the record ids should be separated by FM marker. For example, 1000: FM: 1001: FM etc.

If any select routine have not been attached, all the records will be selected and converted into CSV files by default.

PROCESS API
SUBROUTINE DW.XX.PROCESS.API (FILE.NAME, R.DW.EXPORT, T.BI.ID, T.ROW)

Incoming Parameters

FILE.NAME -The name of the file that is going to extracted as CSV file thro DW.EXPORT, For example, CATEG.ENTRY, RE.CRF.MBGL
(where MBGL is GL report head), CUSTOMER etc.,

R.DW.EXPORT - Holds the whole DW.EXPORT record (dynamic array) for the file in FILE.NAME

T.BI.ID - Holds the Record id to be processed in the PROCESS routine

Outgoing Parameters

T.ROW -Holds the actual records with field values in the same order that are defined in FILED.NAME of DW.EXPORT record and these
should be separated by FM marker.

Note: By default, this will extract all the fields, whether you define the fields in FIELD.NAME or not in DW.EXPORT,
unless we have any process routine to extract some specific fields values.

Other Records

AC.BALANCES.TYPE
The AA contract exposures are extracted from the t24 application EB.CONTRACT.BALANCES, in that it is bucketed into various AA Soft Asset
types. These Asset types could be that of Principle asset type and Interest/Charge/Fees/Commission Asset types. During Data load in Insight
Risk, System loads the consolidated soft asset Exposures, both Principal and Interest together and updates the transaction table. For the con-
solidation process, Parent Consolidation column is used to consolidate the AA Principle asset type Exposures at the time of data load process.
AA soft asset types are extracted from AC.BALANCE.TYPE and updated in the Asset_Types_T24 table. IN DW.EXPORT, AC.BALANCE.TYPE
record is used to interface the soft asset types into Asset-types-t24 table.

DW.EXPORT - Release R15.000 - Page 27 of 40

PV.ASSET.DETAIL
From R12 T24 release, Provision process is moved in to the separate module PV. Insight risk system updates provision from the table
LN.PROV.BALANCES.DETAILS. To handle Insight Risk Provision process from R12 and later releases, PV.ASSET.DETAIL is extracted from
T24 as this table contains the provision amount details by contracts.

‘PVAD.POST.PROV.AMT’ is the field which is holds the Provision amount in contract currency for each contract if it has provision. And the
‘PVAD.POST.PROV.AMT.LCY’ is holds the Local currency value for provisions if contract currency is not same as reporting currency (Foreign
currency contracts) else it holds null value.

DW.EXPORT - Release R15.000 - Page 28 of 40

Automated tool to configure DW Export utility

Using Automated tool, user can automatically configure for all the records in DW.EXPORT file along with the RE.EXTRACT.PARAMS and
RE.RETURN.EXTRACT files for the GL and the PL CRB reports extracts and setup the same in DW.EXPORT after installing the DW product
and DW Export utility in T24 system.

The automated tool posts set of questions to the user who is configuring the DW Export utility. Based on the inputs given by the user, the sys-
tem configures the DW.EXPORT records along with RE.EXTRACT.PARAMS and RE.RETURN.EXTRACT records for CRB reports of both GL
and PL reports.

This automated configuration utility should only be run from T24 mainline prompt in classic session by typing ˜DW.EXTRACT.CONFIGURE”.

The following questions will be posed to the user:

Welcome to automatic DW.EXPORT configuration utility

Prerequisites
Make sure that the following files which were released as part of DW product are authorised.

STANDARD.SELECTION, EB.API, BATCH, TSA.SERVICE, TSA.WORKLOAD.PROFILE, OFS.SOURCE

Enter any key (except "N") to continue and "N" to exit.

1. In which companies should DW.EXPORT run?

2. Do not type anything for all companies; type each company ID separated with a comma (,).
3. Enter the GL record (a valid RE.STAT.REPORT.HEAD record) that needs to be extracted?
4. GL record is mandatory.
5. Enter the PL record (a valid RE.STAT.REPORT.HEAD record) that needs to be extracted?
6. PL record is optional.
7. Enter the path where the data extract has to be stored?
Enter "DEFAULT" if default path has to be taken (../DwExport-XXX Where XXX is the bank mnemonic), else enter the details for
each company in the following format.

BNK-./DwExport-BNK,GB1-./DwExport-GB1 where BNK and GB1 are the company mnemonics and then a "-" followed by the path.

Separate each company’s path with a comma (,). Underscore (_) is not allowed in the path.

8. Enter the Year and Month based on which CATEG.ENTRY and ACCT.ACTIVITY records will be extracted?
CATEG.ENTRY will be extracted for the year and month (if monthly extract is specified) specified and ACCT.ACTIVITY will be
extracted for the specified year and month and the previous month.

Enter a valid YEAR and MONTH value, the format is YYYYMM, it will not be validated here.

Enter how CATEG.ENTRY records should be extracted? Full extract, Month data or Daily data

Enter 1 for full extract (all the CATEG.ENTRY files will be extracted).

Enter 2 for month extract (CATEG.ENTRY generated in the YEAR and MONTH specified will be extracted).

Enter 3 for daily extract (CATEG.ENTRY generated on the day of extract).

9. How is the extract likely going to happen?

Enter "1" for Online Service

Enter "2" for part of COB process

DW.EXPORT - Release R15.000 - Page 29 of 40

 Enter "3" for Both

Configuring DW.EXPORT...

Note: Two CRB reports need to be configured for Insight - one is for General Ledger and another one is for Profit
and Loss report. Both should be included in DW.EXPORT. For example: MBGL -GL Report, PMPL - P&L Report.

DW.EXPORT - Release R15.000 - Page 30 of 40

MERGE.COMPANY in DW.EXPORT

In an Extended Multi Company Setup, there can be multiple lead companies, and each lead company can have multiple books. In such a setup,
if the records of different lead companies and their books are to be extracted as one consolidated file, the Merge Company option can be used.

However, this is possible only for lead companies that share the CUSTOMER and CURRENCY files.

Users are allowed to configure the MERGE.COMPANY even if the currency files are not shared and all the LEAD.COMPANY have the same
local currency (base currency). MERGE.COMPANY cannot be configured if the LOCAL.CURRENCY across the LEAD.COMPANY is different.

Users are allowed to configure the MERGE.COMPANY if the LOCAL.CURRENCY is the same while the CURRENCY.COMPANY is not same as
the Master Company. A consolidated report can be generated for all the lead companies if the base/local currency are same across the lead com-
panies and all the respective currency rates are equal. The currency rates are loaded from a single data source.

The Merge Company id is specified in the COMPANY record of DW.EXPORT.

In order to consolidate the records of companies US0010001 (BNK) and US001002 (BK2), the merge company’s id is specified in MERGE.CO-
MPANY field of DW.EXPORT.PARAM record.

It can be seen that the CURRENCY and CUSTOMER files are shared between these companies, which is a pre-requisite for Merge Company
extraction.

After specifying the MERGE.COMPANY in DW.EXPORT.PARAM, the DW.EXPORT.SERVICE will be run to extract the CSV files.

DW.EXPORT - Release R15.000 - Page 31 of 40

After extraction, the records of the companies US0010001 and US0010002 are merged and stored under the primary lead company’s mne-
monic (BNK). The Merge Company’s Mnemonic is stored under the BRANCH_CO_MNE field.

Note: If the Merge Company has got branches, the Branch Mnemonic will be updated in BRANCH_CO_MNE field
and the primary lead company mnemonic will be updated in the LEAD_CO_MNE.

Parallel Extraction in DW.EXPORT

In some larger banks with powerful CPUs, whenever larger files such as CUSTOMER, ACCOUNT, and EB.CONTRACT.BALANCES etc., with
millions of records are extracted, the CPUs will not be fully utilized by the extraction process. Hence, this method of Parallel Extraction is
adopted in order to fully utilize the CPU power available in the server.

The Parallel Extraction process is performed in DW.EXPORT by running multiple BATCH processes for data extraction in parallel.

Configure DW.EXPORT
A set of new fields are introduced in DW.EXPORT application which are used for the Parallel Extraction.

The following table explains the new fields introduced in DW.EXPORT that are used for Parallel Extraction

Field Name Description

BULK_NO This field is used to specify number of records to be extracted in one single session, so that sequential file I/O will be
reduced to improve the performance

Allowed values : 1 – 500

BBL_CALL This field is used to call the BATCH.BUILD.LIST to flush out the values in memory and the record ids bulked will be
written into JOB.LIST physically.

Allowed values : 1 – 150

DW.EXPORT - Release R15.000 - Page 32 of 40

Configure BATCH
For the Parallel Extraction process, multiple copies are made for the BATCH record DW.EXPORT.INFO. Different T24 table names can be
defined in each of the BATCH record, so that multiple T24 tables can be extracted simultaneously.

Specify the Table for Parallel Extraction in the DATA field of the BATCH record..

When multiple T24 tables are to be specified in one BATCH record, the table names can be specified in a list record of &SAVEDLISTS& and
the list name can be specified in the DATA field.

DW.EXPORT - Release R15.000 - Page 33 of 40

 Note: If the extraction is performed during COB, the BATCH record for COB (BNK/DW.EXPORT.DETAILS) should
be duplicated and configured in the same way.

Once the BATCH records are configured, corresponding TSA.SERVICE records has to be created for the BATCH records, and SERV-
ICE.CONTROL field should set to START.

Configure BATCH.NEW.COMPANY
Every new BATCH record that has been created should have a corresponding record in BATCH.NEW.COMPANY application. The name of this
record should be identical to that of the BATCH without the Mnemonic. The system will use these records to create branch specific records
when new branches are added to the system.

DW.EXPORT - Release R15.000 - Page 34 of 40

Running TSA.SERVICE
Once the TSA.SERVICE records are configured, the services will be executed simultaneously. It is very important to execute these services in
parallel.

DW.EXPORT - Release R15.000 - Page 35 of 40

The CSV files and the header files are created as the result of the Parallel Extraction. Though multiple services are executed simultaneously,
only one HASH_TOTAL file is created which holds the details of the T24 Tables extracted by all the services.

DW.EXPORT - Release R15.000 - Page 36 of 40

FAQs

1. Daily extract is configured for STMT.ENTRY, CATEG.ENTRY and RE.CONSOL.SPEC.ENTRY in DW.EXPORT. However, the cor-
responding CSV files do not have any data. What could be the possible cause?

The field ENT.TODAY.UPDATE in the SYSTEM record of ACCOUNT.PARAMETER is set to NO. This must be changed to ˜YES” in
order to enable the updates to related tables that support daily extraction.

2. Does DW process clear the data in the export directory (configured in FILE.PATHNAME) automatically?
Yes, whenever the DW process starts, the primary step is to clear the export directory. Hence no manual intervention is required.

3. What is the performance benchmark of DW jobs, what is the idle number of agents which should be assigned to the DW.E-
XPORT.SERVICE?

The DW extraction process has been fine tuned out of box. When the extraction is performed as part of COB, it would use the agents
that are allocated to the COB, and takes the nominal time to complete the process.

When the process is disabled from COB and the online service DW.EXPORT.SERVICE is chosen for extraction, the bank IT team has
to test the performance of DW.EXPORT.SERVICE by assigning the number of agents from a minimum to the maximum value, which is
normally used by COB.

Based on the results, the bank IT team would need to setup the performance benchmark of service specific to the bank.

To improve the performance of the extract, there is a parallel extraction

4. Does assigning the more number of agents to DW service causes the locking issues?
No, it will not cause any locking issues.

5. Does running the DW service causes any locking issues on application files while the bank is started operating the business?
No, it will not cause any locking issues on applications files. Therefore it can be run in parallel.

6. Is there a way to reset the DW.EXPORT.SERVICE when it stops abnormally, which avoids the process of restoring the pre data back
up?

a. Yes, there is a way to reset the DW.EXPORT.SERVICE

b. The relevant BATCH.STATUS should be deleted

c. The relevant F.LOCKING records should be deleted

d. The relevant JOB.LIST should be cleared.

e. The BATCH record should be reset manually.

Note: This is not the recommended option to the Bank; only experienced users can perform these steps as
incorrect usage can result in data loss.

7. Is there any process available to reconcile the HASH_TOTAL.csv file without doing manual check up on HASH_TOTAL figures?
Currently, there is no automated process to reconcile the HASH_TOTAL figures, it must be done manually.

8. How to get the license code to install DW.EXPORT?

Contact Temenos support through TCSP or get in touch with the licensing team (l&[email protected])

9. Typing each FIELD.NAME is too tedious, while creating a record in DW.EXPORT. Is there a short-cut to include all field names in the
table?

Use the keyword ˜SYSTEM FIELD in the FIELD.NAME field and commit the record, the system will automatically include all the
fields in the extraction.

DW.EXPORT - Release R15.000 - Page 37 of 40

10. Is it possible to change the field delimiter from ˜~ to some other character?
No, the delimiter should not be changed, because this is the delimiter that is used by Insight when processing the data.

11. Does DW.EXPORT support Unicode character-set?

Yes, DW.EXPORT supports Unicode Character set. This is handled by the jBase variables JBASE_ CODEPAGE and JBASE_ I18N.
These variables should be set correctly at the jBase level.

12. Is it possible to have different set of extracts from the same table?
Yes, from R11 onwards, different sets of extract are possible for the same table. The record in DW.EXPORT should be of the format
<table name>-<user defined string>.For example: ACCOUNT-HIS

13. Is it possible to write my own SELECT/PROCESS API? If yes, how?

Yes, it is possible to use a user defined, PROCESS / SELECT APIs. Refer the ˜DW.EXPORT API section in the user guide. Refer the
SAMPLE APIs released as part of updates/Patch for any further details.

14. Is it possible to extract data from a New Table in T24 using DW.EXPORT?
a. Yes, data can be extracted from any table in T24. The New Table should be specified as a new record in
DW.EXPORT application. Follow these steps to add a new table.
b. Create a new record in DW.EXPORT with the new tables name

c. Specify the following information in the new record

d. Provide a description for the new table; this is a free text field
e. Specify the COMPANY for which this table is to be extracted in the SEL.COMPANY field.
f. SELECTION.RTN and PROCESS.RTN should be blank for the new table
g. Specify ˜SYSTEM FIELD in the FIELD.NAME field. This will enable the system to include all the fields of the
table for extraction

DW.EXPORT - Release R15.000 - Page 38 of 40

 h. Specify ˜Y in the TAKEOVER field

i. Commit the Record and run the extraction process. The table will be extracted as a separate CSV file.

15. My DW.EXPORT process terminated abnormally. On restart, “_ Fatal error in OPF error NO FILE.CONTROL RECORD” error
occurred. How to fix this?

There could be many causes for abnormal process termination. This should be analysed by Temenos Support to identify the root cause
and provide a solution. Log an issue with TCSP Portal

16. Is it possible to automate transfer of extracts to Insight server using SFTP? If yes, how?
Yes, the transfer can be automated using SFTP. A sample SFTP routine is provided by Temenos. However, this is not a complete ftp
solution; hence the bank should own the routine and can do any changes to that routine to incorporate more securities in the transfer
process.

17. When the extract is transferred from T24 to Insight server, which transfer mode should be chosen for “ASCII or Binary"?
While transferring data from T24 to Insight Server using FTP, always ˜Binary mode” should be used.

18. Under debug mode, when tSA agents are started, it stops without extracting any data. Which are the areas that need to check?
Check if TAKEOVER field is set or not for all the record configured in DW.EXPORT

Check if the BATCH job DW.EXPORT.INFO is set to ˜D in BATCH record DW.EXPORT.DETAILS for COB or DW.E-
XPORT.SERVICE for online service.

19. DW.EXPORT extracted all data but HASH_TOTAL.csv is missing. What could have gone wrong?
The DW.EXPORT.SERVICE could have stopped abnormally. In such case, refer question 7 to reset the DW.EXPORT.SERVICE and
run the service again.

20. RE.CRF record(s) is correctly setup as per the user guide. But the extract file is not being generated. What could be the root cause?

DW.EXPORT - Release R15.000 - Page 39 of 40

 The GL report may not be available in T24. Run the RE.RETURN.EXTRACT service to generate the GL report and then run the DW.E-
XPORT extraction.

21. Is it possible to use Daily extract for any T24 Table that has got a Concat file?
Yes, by specifying a valid CONCAT file for the table, daily extract can be performed for any T24 table.

•Note:Two CRB reports need to be configured for Insight “ one is for General Ledger and another one is for Profit
and Loss report. Both should be included in DW.EXPORT. For example MBGL “ GL Report, PMPL “ P&L Report.

…Where XXX is the company mnemonic and YYYY is the standard T24 report available in RE.STAT.REPORT.HEAD
application.

DW.EXPORT - Release R15.000 - Page 40 of 40