T24 Data Migration Tool – Service Mode

This guide aims at explaining the functionality of a non-core T24 Data Migration Tool that is
used for Data Upload into T24 from any legacy system.

Introduction

The T24 Data Migration tool was originally written using the EB.PHANTOM option. Phantom
processing in T24 is gradually moving from EB.PHANTOM to TSA.SERVICE. The Data
Migration tool too has been modified to be run as a Service. The original functionalities of

 Multi threaded transaction takeover

 Takeover performance reporting, have been preserved in the latest version.

Product Overview

The T24 Data Migration tool will be used during the pre-Live in any site implementations. It
basically covers the following functionalities.

 Used the Standard OFS module to perform the Upload. The Option is given to use
either OFS or standard jBase WRITE function to perform the Upload.

 Validations done on the data, prior to update.

 Accepts data in any layout and format, that includes double byte characters (Provided
the jBase used for the implementation is 4.1 or higher)

 Required less manual intervention during mapping of the incoming file to T24
applications, which is a one time setup.

 Supports upload of Local Tables too that are site specific

 Perform all standard T24 validations and also includes any special cases to perform
local validations for the data being uploaded.
  Supports scaling, using the multi threading capabilities of TSA.SERVICE. However,
this is dependent more on the hardware capabilities.

 Stop/Resume options in case the Server/T24/Database connectivity is lost in the middle

of the upload. In this case, the operation will be resumed from where it was paused.
Standard TSA.SERVICE transaction management capabilities are available.

 Exception Handling is done to report any erroneous data present in the Data file.
This report also includes detailed description of the error that is raised during the
upload.

Tables

The T24 Data Migration tool package consists of the following Tables

DM.MAPPING.DEFINITION

This application allows the user to define the format of the data in the incoming tape. The
following provides the list of fields and the associated description.

No. Field Name Description

The id of this application is free format text, 35
characters long.

A meaningful ID, indicating the application name

e.g. CUSTOMER and any subdivisions E.g. IND –
@ID
Individuals, CORP- Corporate etc should be
provided.

CUSTOMER-IND CUSTOMER-CORP

1 GB. DESCRIPTION Free text Description to describe the Upload.

2 Name of the T24 Table to which the Data is been
APPLICATION.NAME uploaded.
3 Either „OFS‟ or „WRITE‟ to specify if the
LOAD.TYPE upload is via OFS module or jBASE Write
function
A value “VALIDATE” will just validate the
4 OFS.ACTION contents of the data if it fits into T24 table.
Value is allowed in this field only when
LOAD.TYPE is set to OFS
The following FUNCTION are allowed to be
5 OFS.FUNCTION
specified to be used by the OFS to process the
transaction. (I, R, A, D). “I” is taken as default.
6 FILE.TYPE The Type of T24 file to be updated. Values could
 be $NAU, LIVE or $HIS. Value is allowed
only when the LOAD.TYPE is set to WRITE
The T24 Application’s Version to be used
7 OFS.VERSION when uploading through OFS. Value is allowed
in this field only when LOAD.TYPE is set to
OFS
8 To define the way in which the fields are
IN.DATA.DEF read. Either DELIM or POSITION or OFS
The Delimiter used to identify each fields in
the data.
9 FM.DELIM
Value allowed only when IN.DATA.DEF is set
to DELIM

The Delimiter used to identify each multi-value

10 VM.DELIM fields in the data. Value allowed only when
IN.DATA.DEF is set to DELIM
The Delimiter used to identify each sub-value
11 SM.DELIM fields in the data. Value allowed only when
IN.DATA.DEF is set to DELIM
When a particular character in the incoming data
12 ESC.SEQ.FR needs to be converted, the character to be
converted must be provided here.
Works in conjunction with ESC.SEQ.FR, this is
13 ESC.SCR.TO the character to which the ESC.SEQ.FR character
will be converted.
Either “AUTO” (which system takes care to
generate the ID) “DATA” (hardcoded ID in the
14 ID.TYPE
coming file itself) “ROUTINE” (A routine
attached that forms the ID)
The Routine that forms the ID for each record
15 ID.ROUTINE uploaded. Value allowed only when ID.TYPE is
set to ROUTINE
The position in which the ID of each record can be
16 ID.POSITION found. Value allowed only when ID.TYPE is set to
DATA
The Length of the ID in each record in the data
file.

Value allowed only when ID.TYPE is set to DATA

17 ID.LENGTH
Note – This field is used in reference with
ID.POSITION to get the data for the ID from the
raw file

The field name in the T24 table to which the data

18.1 APPL.FIELD.NAME is updated (Associated multi-value set till 24.1)
 The starting position of the data that will be
updated in the T24 field (Associated multi-value
19.1 FIELD.POSITION set till 24.1). Associated multi-value set till 24.1).
Value allowed only when IN.DATA.DEF is set to
POSITION
The length of the data that will be updated in the
T24 field (Associated multi-value set till 24.1).
Associated multi-value set till 24.1). Value
allowed only when IN.DATA.DEF is set to
POSITION
20.1 FIELD.LENGTH
Note – This field is used in reference with

FIELD.POSITION to get the data for the field

from the raw file

Either “ROUTINE‟ – indicated the data will be

formed from the routine for this field (or)
21.1 FIELD.ATTRIB
“CONSTANT‟ – a static value that will be
updated for the field
The Static value that will be updated for the
22.1 FIELD.VALUE field. Value allowed only when FIELD.ATTRIB
is set to CONSTANT
The Post update routine , used a s a user exit
23 POST.UPDATE.RTN routine that will be triggered for every record that
is been uploaded
The OFS source record to be used when uploading
data into T24. Two OFS Source records,

1. DM.OFS.SRC
24 OFS.SOURCE
2. DM.OFS.SRC.VAL – With FIELD.VAL set
to “YES‟ for cases where field validation
processing must be triggered e.g.
AC.ACCOUNT.LINK are provided by default.

DM.SERVICE.CONTROL

This application is used

 To define the company for which the data is uploaded

 The location of the incoming data

  Control the execution of the data upload process

The following are the fields and associated description

No. Field Name Description

Must be the same as
@ID DM.MAPPING.DEFINITION
The company for which the data is uploaded. It is
also possible to provide the upload company in the

1 UPLOAD.COMPANY Incoming data. However, once the value is

provided here, this value takes precedence over
incoming data.

The directory where the flat file resides. This must

be a valid directory name, e.g. DATA.BP. Actual
2 FLAT.FILE.DIR
path or relative path of the directory must be
provided
3 The flat file name of the incoming data. Must be
FLAT.FILE.NAME an existing file name
4 No of threads that the TSA.SERVICE must
NO. OF SESSIONS spawn for processing this request.
The status of the process. This can be either

START – Updated automatically by the system

when the DM.SERVICE.CONTROL record is
5 RUN.STATUS “V”erified.
 STOP – Manual stop request to
Stop the take over process.

6 Contains the processing

CONTROL.LOG messages of the Service.
Auto updated