TEMENOS Data Migration Services

Approach, Process and Utilities

Client System T24

Version :28
Date :19 May 2011
Author :TEMENOS Data Migration Team (dm@temenos.com)

Content in this document is subject to change and intended for TEMENOS use only
Please request to dm@temenos.com for the latest version for further circulation
 Introduction

 Governance

 Methodology

 Mapping

 Tools and Procedures

Introduction
What is Data Migration?

 In the information technology world, the data migration is the process of

transferring data from one format to another

 For the Bank and TEMENOS, Data Migration phase involve the

 transition of the business unit’s data from the Client system to T24

 transformation of the data from the Client system to T24 application

 and NOT from Client System database to T24’s database

 The data migration activity starts just after the completion of the business
review

 And completes when

 the migrated data is signed off by the bank’s business team as part of
the Cutover or Go Live conversation reconciliation and

 T24 is ready for its first business day to continue bank’s normal
operation and business
Data Migration Activities

 Data migration as a process, within an implementation of T24, which has been

designed to run as autonomously as possible from the main design and build
process

 Although there is considerable interaction and key dependencies upon the

new system build readiness and design decisions the data migration element
attempts to run as far as possible as a separate sub-project

 A migration process and activity plan is prepared and delivered by the client
to all the stake holders with roles and responsibility to tie-up with the overall
T24 implementation project plan

 Client migration team’s discussion and agreement with client business team
for the scope and process of Extract, Transform(ET) Guideline and Load(L)
Consultancy for each target T24 table or application would be confirmed and
followed by the client migration team for the data cleansing, extract,
transform/staging and preparation of data file for T24 loading
Governance
Roles & Responsibilities (1/2)
 TEMENOS

 Participating in the effort estimation and decision of roles and

responsibility

 Participate in the Kick Off meeting

 Provide the contact mail group for single point of contact
 Provide sample reference documents
 Provide offshore Consultancy in business unit and data mapping to T24
 Provide training in the T24 load tool for loading the data into T24 and T24
extract tool for extracting the data from T24 for reconciliation

 Remote Consultancy for the preparation, testing and cut/switch over

activities

 Defined and limited period onshore consultancy during the execution of

the load of data in T24, if required
Roles & Responsibilities (2/2)
 Client

 Ownership of the entire data migration activities

 Business Unit Mapping – Mapping the existing system business unit to

T24 modules and then to T24 applications

 Client System data mapping - The source of the data from the Client
System should be mapped in the DMS and DES

 Client System data cleansing - Cleanse data in the Client System based
on the field attributes given in the DMS

 Client System data transformation – Transform the Client System data

into T24 data based on definition in the DMS

 Develop Data Extraction program from Client System and prepare the T24
data in staging and prepare the data file for load

 Load of data in T24 & reconciliation of loaded data in T24 and signoff

 Planning & execution of cutover from Client System and satellite systems
Migration Activity Details and Owner
Activity Tasks Owner
Initiation • TDM engagement for migration and provide forecast and raise Resource for Offshore • TEMENOS Project
Work and Resource for onshore Service Team and Client
• Migration Requirement Analysis - Identify T24 base, Target T24 Modules for load and T24
data extract for reconciliation • TDM and Client
• Logistics & Resource planning (H/W, People, etc) • Client
• Testing (TM/DR), Cutover & Reconciliation planning • Client
• Initial Project Plan, Migration Control Matrix ,Effort Estimate distribution, • Client
• Process design, detailed workflows, customizations review and sign off procedures • Client
Mapping • Deliver standard T24 Model Bank Rnn Table definition in DMS • TDM
• Deliver standard T24 Model Bank Rnn Data Extract Specification in DES • TDM
• Mapping Workshops (Video/Audio Conf/Onshore) • Client
• Mapped DMS and DES • Client
Preparation • T24 DM Load Tool configuration based on standard T24 Model Bank Rnn Table
definition in DMS and standard T24 Model Bank Rnn Table definition in DES • TDM
• Data Load Test (DLT) in T24 and Data Extract Test (DET) from T24 with clinical data
based on standard T24 Model Bank Rnn sample Mapped DMS and DES • TDM
• Client System Data Cleansing & transformation (Based on DMS) • Client
• Client System Data Extraction program and staging (Based on DMS and DES) • Client
• Training on the T24 Load Tool • TDM
Testing • Data file generation from staging for T24 Load • Client
• Data file content validation in T24 and provide error details • Client
• Data file content load in T24 • Client
• T24 Data extract for comparison • Client
• Data file error rectification and reconciliation • Client
• Error reporting and management • Client
Cutover • Cutover Data file extraction • Client
• Cutover Data Validation and Load in T24 • Client
• Reconciliation and Sign off • Client
• Go Live • Client
Deliverables (1/3)

 TDM Team

• Sample version of Migration plan for ETL Consultancy (MPP) - MS

Project Plan

• Sample version of Migration Cutover Run book (MCR) – MS Excel

books

• Sample template for Data Migration Approach and Process – MS Word

Document

• Sample template for Data Migration Reconciliation Strategy – MS Word

Document

• Sample Migration Scope Control Matrix (MCM) - MS Excel book

• Standard T24 Model Bank Rnn Table definition in Data Mapping Sheet
(DMS) - MS Excel books
Deliverables (2/3)

• Standard T24 Model Bank Rnn Table definition in T24 Data Extract
Specification (DES) for reconciliation- MS Excel books

• T24 Data Load Test document in Offshore with Clinical Data based on
standard T24 Model Bank Rnn sample Mapped DMS - MS Word
document

• T24 Data Extract Test document in Offshore with Clinical Data based
on standard T24 Model Bank Rnn sample Mapped DES - MS Word
document
Deliverables (3/3)

 Client’s DM Team

 Migration project plan and Cut/Switch over plan

 Provide a single point of contact for all the communication and
deliverables and co ordination

 Sample Data file of the client data in the DMS specific format and
content properties for validation

 Onshore or Offshore consultancy service request with the specific task

or topic with start and end date

 Connectivity – Remote Connectivity and T24 test environment access

 Onshore logistics and resources – Provide LOI, separate work desk,
international dial in telephone, TEMENOS Portal access, etc
Plan

 The plan to understand tasks, dependency, responsibility and time to tie

up with the master project plan.
Reporting

 Administrative reporting by TDM Team

 Daily/weekly publishing of the offshore and onshore work plan with

resources to the TEMENOS Project Manager

 Separate Daily Activity Log for each Migration Consultant

 Weekly work execution report to the TEMENOS Project Manager

 Technical reporting by Client Migration Team

 T24 Migration Tool’ s load and extract reports

 Load Timing Log

 Issue and Risk Log

 Execution report consists of statistics, issues, solution, Lesson

learned and action plan for corrective measures , etc for each
migration exercise
Methodology
Process Definition
 Cutover

 The standard TDM cutover process starting from closing the bank
business on last working day (in client System, mostly a weekend
day) and till the opening of bank business (in T24, on the working
day following the weekend) evaluated and finalised so that entire
cutover should happen within the limited and agreed time-window
accurately

 Data migration

 The standard TDM’s T24 (target system) based documents would be

used and discussed further by the client migration team with the
client‘s business and IT/Operational team to propose and get sign off
for the scope, process and rule for each ET Guideline and L
Consultancy, so that transition from Client System to T24 is achieved
in a smooth and accurate manner with minimal upheaval to the
business
Mapping

 Data Mapping workshops involves the interaction with the Client‘s

business or technical team either via electronic media (Conference call or
video call) or in presence with a pre defined scope and schedule.

 The initial workshops will be done for the identifying scope of the T24
target tables for the corresponding client system business units to arrive
the Migration Control Matrix

 Based on the finalized load table list the DMS’s will be delivered. And the
data mapping session for the each T24 target load tables for all the
required fields will be conducted and explained for the client data
migration team to map with the corresponding client System.

 As out come of these sessions the Mapped DMS and Mapped DES will be
prepared for the client migration team for preparation or configuration of
the DM tool
Technical Approach – General Principles

 Large volume data migration is to be automated (small volume data may

be migrated manually)

 Data transformation or cleansing occurs during extract or staging i.e.

extract logic includes

 Transforming client system data to suit T24 like:

 Account number according to new T24 account number structure
 Product classifications according to T24 categories based on
TAABS
 Cleansing the client system data to suit T24 like:
• 70 character address line into 35 * n number of lines in T24
• Remove / replace characters that are not acceptable in T24 based
on the validation rule
 Build references between T24 data categories (e.g. accounts to
portfolios, security positions to security master) in staging

 Data file content for T24 load with T24 acceptable data at the field level
with the structure defined in DMS
Technical Approach – Staging Area

 The Staging Area data model can be relational but de-normalised. The
tables are designed to resemble the structure of the input files to T24.

 Multi-value fields represented by strings with delimiters (field length set

with maximum occurrence)

Customer Portfolio Account Account

11062 11062-1 11062 01 11062 02

Good Very Good PF1 Very Good Very Good

Staging Very Good … Very Good Very Good

Area
Mr. Very Good 11062 01::11062 02 … …

… … … …

… … … …
Technical Approach – Data Flow

Client Systems T24

Client system T24 software

base
T24
production
Build. # Pre
Environment
Rel. # production
Environment
Copy to Post
Copy

Migration Migration
Environment Activities,
COB and
Release update RECON Client’s
T24
T24 T24
Raw Staging - Data Migration
Client Manual Go Live
Data (Transform Extract Environment
System Extract Data SCP Live Production
Migration &
File Data DM System
Environment Cleansing) Load
File Tool
Secure Automatic
Copy Data load
Protocol

External Satellite Client’s Telekurs T24 Others

Log Files
Client Systems Secured Parameter
System Data
Technical Approach – Single Window Cutover

Preparation Cutover

Fri Fri Sat Sun Mon

EOD
Client System - Post interest
Cust. Accts.
-Post Periodical
Fees

Financial Data
Cust. Static

Acct. Static

Staging

T24 code Pre Validation Migration - Reset

T24 to COB migration
staging
Financials - Reports specific Go
Migration
Area prepare
RECON RECON - Accruals
parameter Post
T24 vs. User T24 vs. - Reval
- Clean-up Live Go-Live
Technical Client Client
CoB System Verification System Clean-up
RECON
T24 System Date is Extract
GL
set to Technical Data to
Working Day Ext. GL Go Live
(Saturday) of the Decision
Cutover week end
Financial Approach – Balances and Take Over Account
Financial Balances
General Ledger L Account Types BS/PL Process in T24 Balance
Migration
Nostros BS Treasury √
Commission PL None
Tax Due on behalf of Customers BS Periodical Tax Payments (e.g. EU Tax) √

Cash in Transit Dividends BS Dividend Processing √

Wash Accounts BS Operations Processes
...

Financial Transaction and Take Over Accounts

Client System T24
Transactions OFS Load
Autom. Extract
MM 10.000, 2,3%, 10.6.2008-10.12.08, Cust Acct 01, Cust Acct 01 3 MM 10.000, 2,3%, 10.6.2008-10.12.08, CCY 14999-4, Cust Acct 01
… 1 4 DC Cust Acct 02, 01.11.08 , CR 25.000 CHF,
5 DC Nostro, 01.11.08,
… 5 Load and book Nostro
Wash Accts OPS Cust Acct X 3 Load and book MM

CR 25.000 CHF MM Take-over MM

Acct XXX CCY 14999-4 P&L Cust Acct 01

GL Account List + Booking Matrices

Load and book 4
Cust Acct Bal Take-over Bal CR Take-over Nostros
Cust Acct 02 CCY 14999-1 Nostros CCY 14999-3
 Mapping

Mapping
What is Mapping?

 Business Unit Mapping with T24 Modules

Preparation of the Module-wise Strategy document with respect to Client

covering the Load Table List and Data Comparison Scope, Various Migration
load Strategies for the client T24 Release.

 T24 Data Mapping Sheet(DMS)

DMS defines the core field properties, help text, field validation, Sample data
inclusion, Pre-requisite & Post Update tables required.

 Mapped DMS

As a outcome of the mapping session Mapped DMS will be derived based on

the T24 target load tables by fields will be conducted and mapped with the
corresponding Client System.
What is Data Mapping Sheet?

 The DMS is to give the complete technical details of ALL the input
able field of a application in T24 and it is dependency and post
update table details

 And have the provision for mapping information from the source
Client System system

 The different worksheets of the DMS are :

 Version

 DMS Details

 Prerequisite

 Data Mapping

 Core Validation Check

 Post Updated Tables

Data Mapping Sheet Details

 DMS Details provide the generic information and prerequisite

 Data Mapping sheet has the following details which is very specific to T24

 T24 Field No

 T24 Field Name

 Field Type

 Field properties

 Help Text

 Sample Data

 Core Validation Check

 Mandatory/Conditional Mandatory (M/C)

 Core Default Value

 Migration Comments

 Client system File name and details

Sample T24 CUSTOMER application - DMS

Worksheet - DMS Details

Sample T24 CUSTOMER application - DMS

Worksheet - Prerequisite
Sample T24 CUSTOMER application - DMS

Worksheet - Data Mapping

Sample T24 CUSTOMER application - DMS

Worksheet - Core Validation Check

Sample T24 CUSTOMER application - DMS

Worksheet - Post Updated Tables

What is Mapped DMS?

 In DMS the client system file and field details should be filled with
respective source data by client’s migration team.
What is T24 Data Extract Specification?

 The T24 Data Extract Specification will be prepared based on the data
comparison requirement which need an automated data extract from T24
after migration of data

 Classification of DES:

 Functional DES - The functional T24 Data Extract requirement and

specification provided by the client based on the functional or business
team requirement apart from T24 standard reports. This based on the
requirement the corresponding T24 fields values in a specified output
format

 Raw Data DES - The raw data extract specification includes all the
fields in the DMS for extracting the loaded data for comparison and
validation against the data file provided for the load
T24 Data Extract Specification Detail

 The different worksheets of the DES are

 Version
 Spec Details

 The Spec Details covers the following details

 Scope
 T24 Extract File Name
 T24 Tables
 Client Extract File Name
 Client Tables
 Header
 Delimiter
 Field Level Details
Sample T24 Data Extract Specification
What is Mapped DES?

 In DES the client system field details should be filled with respective
source data by client’s migration team.
Tools and
Procedures
T24 Data Migration Tools

 T24 Data Load Tool

 Packaged tool for load of data into T24

 Uses generic Open Financial Services (OFS) component of T24

 Loading via OFS is similar to online input of data and hence fully
validated

 Tool accepts data in a text file format - delimited / fixed width

 Exceptions / error logs for review/ rectification

 Capability to handle volumes through multi thread load

 Availability of detailed documentation

 T24 Data Extract Tool

 Extracts data from T24 tables

 Produces data files in agreed format

 Capability to handle volumes through multi thread extract

T24 Data Load Tool (1/2)

 The T24 Data load tool is used to automatically validate the content of the
data file in T24 and load the data during the testing and cutover

 It basically covers the following functionalities and feature

 Required less manual intervention during mapping of the incoming data

file content position to T24™ applications fields, which is a one time
setup

 Automatic configuration based on the Mapped DMS and data file as input

 Sample and full content validations can be done on the data, prior to load

 Supports load of Local tables and Local reference fields that are site
specific

 Perform all standard T24 validations and also can include any special
cases to perform local validation for the data being loaded
T24 Data Load Tool (2/2)

 Supports Multi-Threading load, a very important functionality that

considerably increases the load performance. But this depends on
the hardware capabilities. The number of sessions/threads is user-
defined

 Exception Handling is done to report any erroneous data present in

the data file. This report also includes detailed description of the
error that raised during the load

 Stop/Resume options in case the Server/T24/Database connectivity

is lost in the middle of the load. In this case, the operation will be
resumed from where it was paused

 Provide support to keep the detail information about the load like
number of records, time taken, etc
T24 Load Tool Workflow
Key Components in Data Load (1/6)

 The creation of directories and DSC is done using ‘DM.PREREQUISITE’

Key Components in Data Load (2/6)

 DMV (Data Mapping Verification) which is the T24 table that represents the
Data Mapping Sheet (MS Excel) in T24 for further automatic verification of the
fields specified and the position on data file
Key Components in Data Load (3/6)

 DMD(Data Mapping Definition) contains the list of field names specified and
the corresponding position as per the DMS with T24 table name, load type,
delimiters, OFS function, and the respective migration T24 VERSION, etc
Key Components in Data Load (4/6)

 Versions of the application should be created, which will be used in

the DMD creation
 Separate version records each for Validation , Input, Authorization
should be created
Key Components in Data Load (5/6)

 Data File
 The data file would be extracted from the Client System/staging
system in the specific format with de limiters as per the DMS and will
be copied to DATA.IN directory of the environment used for load
 The data file is generated by the client based on the DMS
 Example for CUSTOMER data file
• T24 directory name ‘DATA.IN’
• Data file name ‘CUSTOM.01‘ with values to all inputable fields as
per the mapped DMS and the content in a single row/line as below
ROW1 1000121|CUSTOME1|CUST1|CUST1|CUST1|STREET1|STREET1|CHENNAI|1|CH|1|840003||1|TEST | Field Marker
FILE||10|1|10|1|1|CH|1|CH|||||||||||20100801M0101|20070101|||1|||CH0010001||||NO|||||MR|TEST1|TESTFAMILY|MALE|200010
11|MARRIED||123456||TEST@TEMENOS.COM|EMPLOYED|BANKER||TEST1|TESTADDR||19980701||25000|||||||||||||CALL|||| :: Value Marker
20010101|TEST CUSTOMER|19990101|ACTIVE|1|||CH||1|2|TEST CUSTOMER||TEST|TEST
CUSTOMER|||||||||||||||M::12345678!!12345683::TEST@TEMENOS.COM::Mr.::::::::::::12345678::12345687::::0::BOTH::Y::CH::Y:
:YES::::::::::::::TEST::20010101::::::::GENEVA::TEST::CHF::::::::::::::::Y::REMITTED BY !! Sub Value Marker
CSC::::::0111100::::123456::1234::12323::Y::REPORTED BY SUMMARY
REPORT::::EMAIL::Y::N::::NC::::::::::123::ABU::::::::::CH::R::0%::::MHA::::::::::N::::::::::::::::::::::Y:::::: 1!!2
::FOUNDATION::1::1::YES::::20050107::WHT::::TEST::TEST::TEST::::::GE::::LT::GE::1::Y::::::::::::1::::DF1::SE1::::::::NAMED::Y:
:::::::::::::::::1::1::HIGH.RISK::::::::::::::::M0101::Y::1::YES::YES::::::::::::::::::::::::::::::::::::::::::::::::::::::::1::Super High Net
Worth::::::::::::::::::::::::::YES::1::YES::::::::::::::::::YES::::::::::::123::1::1::1::PIC
Owner::::1::Company::1::::::::::::::::::::::::::::::::::::::1::1::1::::::::::::::::::::::::::::::::::::19920102::::Y::Y::Y::Y::840001::1::1::1::BANK.OFFI
CE::::::1::20071212::123::::::::::::::::::::::::::::::::::::::CH::::::::::::::::::::YES::YES::YES!!NO::::::::::::::::::::::::::::::::::::::::::::::::::::::::::Y!!Y::1!
!2
ROW2 1000122|CUSTOME2|CUST2|CUST2|CUST2|<Remaining field values>
Key Components in Data Load (6/6)

 DSC(Data Service Control) is the front end to define the data file path,
automatically create the BATCH and the TSA service records to load the data
from the data file to T24 application in service mode
Data file Load Procedure (1/2)

 Place the data file in DATA.IN directory

 DMV record creation based on the Mapped DMS

 DMD record preparation for each load as per the Mapped DMS

 The respective OFS.SOURCE records DM.OFS.SRC, DM.OFS.SRC.VAL,

DM.OFS.SRC.ORD or DM.OFS.SRC.VAL.ORD configured for the validation
control (i.e., field or cross level) and the logs to be created during the data
file while load
 Versions of the application should be created, which will be used in
the DMD creation. Separate version records each for Validation , Input,
Authorization should be created

 DMP record creation to prepare the Validate, Input and authorization

processing directories and DSC automatically
Data file Load Procedure (2/2)

 DSC with the data file directory and data file name is verified to create the
BATCH and TSA record for T24 service processing

 Initiation of service in phantom mode starts the phantom processing in

specified number of agents and validates or loads the data file

 The data file is internally formed as OFS message and passed through OGM
for processing and the errors are captured in different logs as per the agents
and consolidated
T24 Data Load Test

 A test is conducted in offshore with the clinical data that reflect the strategy
and fields mapped in the Mapped DMS to verify the T24 DM tool component
configuration and for the reference during the test loads with real data
 The T24 Data Load Test Documentation (The Bible) covers the following
 Test Scope and Details
 Mapped DMS
 Clinical Data File Extract Details
 DM Tool Details
 Data Migration Procedures
 Pre-requisite, Directory, DSC Creation
 Validation, Input & Authorization
 Significance of the loaded Records
 Post updated T24 tables & Characteristics
 Life cycles - COB
Sample Data File Load - CUSTOMER

 Sample Customer Data File

 The creation of directories and DSC is done using

‘DM.PREREQUISITE’
Stages of Load

Validation

Input

Authorization
Validation

 Status of Services
 Run Service
 Monitor agent & Process Status
 Validation Status
 Record Count
Status of Services

 The status of the services should be monitored to ensure no other

services are in running status.

 Use the following enquiry to check the status of the services

Status of Services
Run Service

 The DM Service Control (DSC) should be verified to start the

validation
Run Service

 Status of the service will be START after the record has been
verified
Run Service

 Start the T24 Service Manager (TSM) which will initiate the T24
Service Agents (TSA) for the service to run
Monitor Agent & Process Status

 The status of the Agent & Process can be monitored using the
following ENQUIRY
DM.SERVICE.CONTROL Status

 Status of the service will be STOP after the service has been
completed.
Validation Results – CUSTOMER (1/3)

 The entire data file is first validated with VALIDATE option in order to identify
the errors. The error details will be captured in DSC
Validation Results – CUSTOMER (2/3)

 The errors will be captured in the error logs in the respective path.
ORD(OFS.REQUEST.DETAIL) can also be used to check the result of
validation.
Validation Results – CUSTOMER (3/3)

 The corrected data file should be placed in the VALIDATE02

directory

 And the corrected data will be subjected to further validations

until all records are validated successfully
Input

 Status of Services
 Run Service
 Monitor agent & Process Status
 Load Status
 Record Count
Status of Services

 The status of the services should be monitored to ensure no other

services are in running status

 Use the following command to check the status of the services

Run Service

 The DM Service Control (DSC) should be verified to start the

validation
Run Service

 Status of the service will be START after the record has been
verified
Run Service

 Start the T24 Service Manager (TSM) which will initiate the T24
Service Agents (TSA) for the service to run
Monitor Agent & Process Status

 The status of the Agent & Process can be monitored using the
following command
DM.SERVICE.CONTROL Status

 Status of the service will be STOP after the service has been
completed.
Authorization

 Since CUSTOMER is a static application, the load is with 0 level

authorization, i.e. the records are authorized during input through
load itself and hence separate authorization is not required.
Authorized Record

 The authorized record screenshot is given below, which matches

the value in the data file
Authorized Record
Data Extraction – Generic Approach

 The approach of data extraction in

migration is Target system based
approach i.e. T24 data extract is
compared against the Client System. The
generic approach of extract from T24 is
derived based on the usage of standard
migration process and on the experience
of the repeated execution of the best
practices.

 The existing T24 Enquiries are also used

to verify the loaded data. In addition as
part of Sign off for the migration the
loaded data is compared against the
client system by the bank.
T24 Data Extract Specification (DES)

 The T24 Data Extract Specification is the base file used to get the
information on the fields to be extracted after the load of data for checking
the correctness of the data loaded / comparison between the client system
and T24 extract

 Based on the DES the Extractor tool will be configured and the Data Extract
Test Document (DET) will be provided with clinical data and sample output
and signed-off by the Client and then the extractions will be done in the
client’s T24 environment.

 The classification of Data Extracts are:

o Raw data

o Functional
DES - Spec Details Work Sheet
Data Reconciliation Methodology

 Data reconciliation in TEMENOS Data Migration is Target T24 Rnn system

based approach i.e. T24 data extract against the client system.

 Classification of Data Reconciliation:

 Manual - It is basically performed for the applications which has less

volume of data. The strategy for manual reconciliation is derived in a
such way that the scope, sampling, resource requirement, execution
time, etc., need to be documented based on the client requirement.

 Semi-Automatic – The data extraction from the client system and the
comparison is carried out by a specific utility developed by the client
migration team to derive the data file as per the format in the DES
T24 Data Extract Tool

 The T24 Extract tool is used to automatically extract the content of the
T24 file and used to provide to the Client to compare the data during the
testing and cutover.

 It basically covers the following functionalities and feature

 Required less manual intervention during mapping for the outgoing

data file content position from T24 applications fields, which is a one
time setup.

 Automatic configuration based on the Mapped DES and data file name
required in the output

 Supports the extract of Local tables and Local reference fields that
are site specific

 The different stage are of the extraction: Selection, Extraction,

Preparation, and Output.
Key Components for T24 Data Extract

 DM.EXTRACTOR is the table to define the fields that are need to be

extracted, the separators to be used, path to place the extracted file are all
defined in this table based on Mapped DES

 TSA.WORKLOAD.PROFILE is updated/created with Id as DM.EXTRACTOR-

<ID of DM.EXTRACTOR>

 TSA.SERVICE is updated/created with Id as DM.EXTRACTOR-<ID of

DM.EXTRACTOR>

 BATCH is updated/created with Id as DM.EXTRACTOR-<ID of

DM.EXTRACTOR>
T24 Data Extraction Procedure

 BATCH, TSA.SERVICE and TSA.WORKLOAD.PROFILE records will be

created automatically upon authorization of DM.EXTRACTOR.

 To get the extracted output as per the agreed format the service
DM.EXTRACTOR-ACCOUNT has to be initiated in the phantom mode .

 The service can be initiated to get the data extract output.

 On completion of the service the output files will be created in the

respective directories as specified in DM.EXTRACTOR
Sample DM.EXTRACTOR for Cash Balance data extract
Sample DM.EXTRACTOR for Cash Balance data extract
T24 Data Extract - Sample Output
TEMENOS Data Migration Team

Contact : dm@temenos.com