3) Template, Fields and Description PDF

8/5/2021 Template, Fields and Description
You are here: Country Regional Solutions > Global > Data Migration Tool > Template, Fields and Description
https://tcsp.temenos.com/R19CD/R19CD.htm#../Subsystems/R19CMUG/Content/CountryPacks/Generic/DataMigrationTool/Template, Fields and De… 1/14

Template, Fields and Description
DM.INFORMATION
Counting the number of records for every application, before and after migration, is a vital part of Data Migration .The
information of the number of counts per application is available in a Live file DATA.MIG.COUNT. This application keeps
track of the changes in the load count.
The entire operation can be successfully complete using the Browser.
No. Field Name Description
@ID ID must be SYSTEM.
1.1 CLIENT.NAME The name of the client for which the migration is to be done
2.1 DESCRIPTION The descriptions of your report set / interface.
3 MIG.TYPE The migration type that is going to be done (E.g. TM0, DR1, LIVE)
4 SELECT.LIST This is an optional filed, where a valid &SAVEDLISTS& name can be given.
5 MNEMONIC Specify the company Mnemonic
6.1 APPLICATION This is a multivalue set where we should provide the Application Names
for which the count is to be done
7.1 LIVE.COUNT This is an associated multivalue set where the number of records in LIVE
file will be populated.
8.1 NAU.COUNT This is an associated multivalue set where the number of records in NAU
9.1 HIS.COUNT This is an associated multivalue set where the number of records in HIS
10 OVERRIDE Overrides that are generated, if any.
DM.DATA.TRANSLATION
The data provided by the Client will contain values that correspond to the Legacy Data Format which cannot be loaded
into T24 without any TRANSLATION. Hence a valid TRANSLATION must be done so that the Data is converted into a T24
Data format and can be loaded. The application DM.DATA.TRANSLATION is used for converting legacy data into T24
format.
@ID The id should be the valid Directory inside the DATA.IN directory.
Creation of directory [DATA.IN] is covered as part of Installation
guide.The id allows 25 characters long
1 APPLICATION The application for which the conversion carried out.
2 SOURCE.DIR The source directory of the data file consisting of Legacy ID is

provided in this field
3 SOURCE.FNAME The Data file name consisting of Legacy ID is given.
4 TARGET.DIR The name of the output directory where the converted file will be
available after the conversion is over. Any error log generated will be
available as mentioned above.
By default DATA.IN can be provided
or modified as per the user.
5 TARGET.FNAME The name of the converted data file with T24 Ids must be given
here.
6 FM.DELIM The Field Marker that is used in the datafile to delimit field values.
By default ‘|’ is defaulted which can be modified as per the user.

7 VM.DELIM The Value Marker that is used in the datafile to delimit field values.
By default ‘::’ is defaulted which can be modified as per the user.
8 SM.DELIM The Sub Value Marker that is used in the datafile to delimit field
values. By default ‘!!’ is defaulted which can be modified as per the
user.
9.1 MAPPING.TABLE Any Concat file name that will be used for the conversion can be
provided in this field. This is a multivalue field.
10.1.1 POS.CONVERT The positions in the datafile where the conversion has to be done
and replaced with T24 Ids. This is a sub value field associated with
Mapping Table field.
11.1.1 POS.VALUE The positions in the data file where the conversion values are
defined .This is a sub value field associated field.
12.1.1 POS.ROUTINE A subroutine can be attached to this field that will be used for
conversion logic. This is an associated sub value set with Position
Check field. This is a sub value field associated field.
13 NO.OF.SERVICE The number of agents that will be required to run the conversion
can be mentioned in this field. Default value is 16
DM.PREREQUISITE
This table is used to create folders and for copying of data files to the respective folders and creating the
DM.SERVICE.CONTROL (DSC) that are necessary for the load of Data to T24. Using the application DM.PREREQUISITE we
can create necessary folders and moves the data files to their respective paths. We will also be able to create folders for
placing reconciliation extracts from T24.
@ID A 3 digit number followed by an asterisk (*), followed by a

valid user name that must be present in the USER table
1 DESCRIPTION Free text Description.
2 PROCESS The task that will be done when the application is verified.
Either creation of DSCs or Only creation of Directories or Both
can be specified here.
3 RESERVED.5 Future Use
4 DIRECTORY.NAME The directory name where the data files are stored and under
this directory will other folders get created which will be used
as Path Name in DM.SERVICE.CONTROL. The value DATA.IN is
defaulted, which can be changed to any other directory as
and when needed.
5 SELECT.LIST This is an optional filed, where a valid &SAVEDLISTS& name

can be given
6.1 DMD.NAME This is an Associated Multivalue set which will hold the DMD
name for which the DM.SERVICE.CONTROL will be created
followed by a dot (.) and a two digit sequence number. (The
format is mandatory). The folders that need to be created for
the data file will be based on the input to this field.

7.1 FILE.NAME
This is an Associated Multivalue set .The
data file that will be used for the load will be
selected automatically based on the input in
the previous field. The data file must be
present in the Directory that has been
specified in the field Directory Name. The
format of the data file must be as follows.
<dmd.name>.<2 digit number>.
<yyyymmddhhmm>.TXT
E.g.: CUSTOM.01.201203031653.txt
12 RECONCILIATION We need to specify if Reconciliation Folders are to be created

or not. By default, the value “No” is defaulted.
13 RECON.DIR The Directory name must be specified here where the

reconciliation folders will be created. By default RECON.OUT
is populated in this field.
14.1 RECON.SPEC.NAME This is a multivalue field that is used to provide the Names of
the folders that need to be created under the Directory
specified in the field Recon Dir.
15.1 DM.EXTRACTOR.NAME This is a multivalue field that contains DM Extractor Id. The
value entered must exist in the DM.EXTRACTOR table
16 FILE.CONV.REQD File conversion will be done if this field is set to YES.
17 FILE.LOAD.TYPE This field specifies whether the file load is from Server or
Local host
18 CONVERSION.TYPE Conversion type is specified here. Values entered here are NT

or Unix
DATA.MAPPING.VERIFICATION
Verifying the correctness of the Data Mapping Table and the DM.MAPPING.DEFINITION is a vital part of Data Migration,
without which the data load, could go wrong. DATA.MAPPING.VERIFICATION verifies, whether the Data Mapping Table
and the DM.MAPPING.DEFINITION are in synchronisation.
This application also produces an output file in the specified DMV directory with the status of the Verification.
@ID
The id of this application is free format text, 12
characters long.
A meaningful ID, indicating
the application name e.g.,
CUSTOMER should be provided.
CUSTOMER
MM.MONEY.MARKET
LIMIT
1 DESCRIPTION Free text Description.
2 APPLICATION.NAME Name of the T24™ Table to which the Data is been loaded.
3 DMD.NAME DMD Name to be specified.
4 DIRECTORY.NAME The Directory name where the DMV status result will be stored.

5 MAPPING.STATUS This field gets updated on verification of the record with PASS or
FAIL status.
If the fields in DMD and the one in save list are same
without any mismatch then it would be updated as PASS.
6 CORE.LIST This is the name of the file where the core fields are given for
comparison. This file is to be placed in DATA.IN.
7 LOCAL.LIST This is the name of the file where the local fields if any are given
for comparison. This file is to be placed in DATA.IN.
8.1 CORE.FIELDS This is an associated Multivalued field which gets updated with
the fields in the CORE.LIST i.e the Core fields upon verification.
CO.FIELD.STATUS The Delimiter used to identify each multi-value field in the data.
9.1 Value allowed only when IN.DATA.DEF is set to DELIM. This is an
associated Multivalued field
10.1 LOCAL.FIELDS This is a Multivalue field which gets updated with the fields in
the LOCAL.LIST i.e the local fields upon verification
11 DATAFILE.NAME This field specifies the Data file name. The file has to be placed
in DMV directory.
12 VERIFICATION.TYPE This field becomes mandatory on providing value for the field
DATAFILE.NAME.Values allowed is FIRST,POSITION,RANDOM.
13 FIRST.POSITION This field becomes Mandatory on specifying POSITION in

VERIFICATION.TYPE.This field specifies the position from where
verification has to be done for the file.
14 LAST.POSITION This field becomes Mandatory on specifying POSITION in

VERIFICATION.TYPE.This field specifies the position till where
verification has to be done for the file
15 DATAFILE.COUNT The number of records in datafile will be updated here.
16 ERROR.DESC If there is any error then the error message will be populated on
verifying the record.
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, positions and the associated description.
@ID
characters long.
A meaningful ID, indicating the application
name e.g. first six characters of the application
name, CUSTOMER and the Load process,
should be provided.
V.CUSTOM
A.CUSTOM
I.CUSTOM
1 GB. DESCRIPTION Free text Description to describe the Load.
2 APPLICATION.NAME Name of the T24™ Table to which the Data is been loaded.
3 LOAD.TYPE Either ‘OFS’ or ‘WRITE’ or ‘READ.REPLACEMENT’ to specify if the

load is via OFS module or jBASE Write function or the
replacement of a few fields.

4 OFS.ACTION A value ‘VALIDATE’ or ‘PROCESS’ will just validate/ process the

contents of the data if it fits into T24™ table. Value is allowed in
this field only when LOAD.TYPE is set to OFS.
5 OFS.FUNCTION The following FUNCTIONS are allowed to be 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™ files to be updated. Values could be $NAU,

LIVE or $HIS. Value is allowed only when the LOAD.TYPE is set to
WRITE or READ.REPLACEMENT.
7 OFS.VERSION The T24™ Application’s Version to be used when loading

through OFS. Value is allowed in this field only when LOAD.TYPE
is set to OFS
8 IN.DATA.DEF To define the way in which the fields are read. Either DELIM or
POSITION or OFS
9 FM.DELIM The Delimiter used to identify each fields in the data. Value
allowed only when IN.DATA.DEF is set to DELIM
10 VM.DELIM The Delimiter used to identify each multi-value field in the data.
Value allowed only when IN.DATA.DEF is set to DELIM
11 SM.DELIM The Delimiter used to identify each sub-value fields in the data.
Value allowed only when IN.DATA.DEF is set to DELIM
12 ESC.SEQ.FR When a particular character in the incoming data needs to be

converted, the character to be converted must be provided
here.
13 ESC.SCR.TO Works in conjunction with ESC.SEQ.FR, this is the character to

which the ESC.SEQ.FR character will be converted.
14 ID.TYPE Either ‘AUTO’ (which system takes care to generate the ID)
‘DATA’ (hardcoded ID in the coming file itself) ‘ROUTINE’ (A
routine attached that forms the ID)
15 ID.ROUTINE The Routine that forms the ID for each record loaded. Value
allowed only when ID.TYPE is set to ROUTINE
16 ID.POSITION The position in which the ID of each record can be found. Value
allowed only when ID.TYPE is set to DATA
17 ID.LENGTH
The Length of the ID in each record in the data
file. Value allowed only when ID.TYPE is set to
DATA.
Note – This field is used in reference with
ID.POSITION to get the data for the ID from
the raw file
18.1 APPL.FIELD.NAME
The field name in the T24™ table to which the
data is updated. 65 characters long
(Associated multi-value set till 22.1).
This field allows to accept the field names and
field positions of the application. For local
reference field, Use the local field name and
not the position.
T
o define the fields from LD.SCHEDULES.DEFINE
use the respective field names only .
19.1 FIELD.POSITION The starting position of the data that will be updated in the
T24™ field (Associated multi-value set till 24.1). Associated
multi-value set till 22.1). Value allowed only when IN.DATA.DEF
is set to POSITION

20.1 FIELD.LENGTH
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 22.1).
Value allowed only when IN.DATA.DEF is set to
POSITION.
Note – This field is used in reference with
FIELD.POSITION to get the data for the field
from the raw file
21.1 FIELD.ATTRIB Either ‘ROUTINE’ – indicated the data will be formed from the
routine for this field (or) ‘CONSTANT’ – a static value that will be
updated for the field
22.1 FIELD.VALUE The Static value that will be updated for the field. Value allowed
only when FIELD.ATTRIB is set to CONSTANT
23 POST.UPDATE.RTN The Post update routine , used a s a user exit routine that will be
triggered for every record that is been loaded
24 OFS.SOURCE
The OFS source record to be used when
loading data into T24. Two OFS Source records,
1. DM.OFS.SRC
2. DM.OFS.SRC.VAL
3. DM.OFS.SRC.ORD
4. DM.OFS.SRC.VAL.ORD
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 loaded.
The location of the incoming data control the execution of the data load process.
The following are the fields and associated description.
@ID
Must be the same as
DM.MAPPING.DEFINITION.
1 UPLOAD.COMPANY The company for which the data is loaded. It is also possible to
provide the load company in the Incoming data. However, once
the value is provided here, this value takes precedence over
incoming data.
2 FLAT.FILE.DIR The directory where the flat file resides. This must be a valid
directory name, e.g. DATA.BP. Actual path or relative path of the
directory must be provided.
3 FLAT.FILE.NAME The flat file name of the incoming data. Must be an existing file
name.
4 SERVER.NAME Specifies the name of the server, for multiple application servers

5 USER The user name which will be used for the load process. This
username will get updated in the TSA.SERVICE record related to
the DM.SERVICCE.CONTROL.
6 NO. OF SESSIONS No of threads that the TSA.SERVICE must spawn for processing
this request.
7 MOVE.TO.HIST The field MOVE.TO.HIST is to move the error details from DSC to
another template namely DM.SERVICE.CONTROL.HIST
10 RUN.STATUS
The status of the process. This can be either
• START – Updated automatically by the system
when the DM.SERVICE.CONTROL record is
‘Verified.
• STOP – Manual stop request to stop the
takeover process.
11 DSC.TYPE Dsc type should be either DMD or DME
12 PRE.PROCESS This field is used to run the DM.PRE.PROCESS service as multi-

threaded or single threaded. It is a mandatory field. The values
accept as SINGLE or MULTI. For sequential file upload this type
should be ‘SINGLE’.
15.1.1 CONTROL.LOG Contains the processing messages of the Service. Auto updated.
16.1 ERROR.DETAILS The errors that have been generated after the completion of the
process will be captured in this field. Auto updated.
17.1 NO.OF.ERROR The number of errors that have been recorded after the
completion of the process will be captured in this field. Auto
updated.
18.1 TYPE.OF.ERROR The type of errors consolidated from all the errors generated
after the completion of the process will be captured in this field.
Auto updated.
19 ERROR.FILE.PATH If the error is generated, this field will indicate the path where
the error long gets stored. Auto Updated.
20 ERROR.FILE.NAME If the error is generated, this field will indicate the file name of
the error long gets stored. Auto Updated.
21 DATE The current date of the load process will be updated in this field.
Auto updated.
22 STARTED The current start date/ time of the load process will be updated
in this field. Auto updated.
23 STOPPED The current end date/ time of the load process will be updated in
this field. Auto updated.
24 ELAPSED The current elapsed date/ time of the load process will be
updated in this field. Auto updated.
DM.SERVICE.SCHEDULER
The services for validating, loading and authorizing of Data in T24 is required to be scheduled and automated. Most of
the tasks are manually performed which needs to be eliminated. The multithread service will perform the tasks in an
automated way to eliminate the manual task to an extent.

@ID
The ID for this application must be a user
defined name for the SCHEDULER.
e.g.: DSS.STATIC
1.1 DESCRIPTION The description of the SCHEDULER.
2 DSS.TYPE To indicate whether the service needs to be run for

DM.MAPPING.DEFINITION or DM.EXTRACTOR. It accepts values
as DMD or DME
3 VERIFICATION.DSS The DM.SERVICE.SCHEDULER table record which needs to be

completed successfully in order for the current service to be
started.
4 RUN.STATUS To indicate whether the service needs to be started or stopped.

The two options available are START and STOP.
5.1 DM.SERVICE.ID To store the DM.SERVICE.CONTROL table record which needs to

be started
6.1 VERIFICATION To store the DM.SERVICE.CONTROL table record which needs to

be completed successfully in order for the service, associated
to the multivalued set, to be started
7.1 CURRENT.DIRECTORY To store the specified data file path for that services. This is an
associated multi-value field.
8.1 DATA.FILE.NAME To specify the data file name for validate or load the data. This
is an associated multi-value field.
9.1 NEW.DIRECTORY To specify the new data file path for that services. This is an
associated multi-value field.
10.1 ERR.THRESHOLD To specify the maximum number of errors that will be tolerated
before marking the service as failed.
11 NO.OF.ERRORS No input field to update the number of records in error from

the corresponding DM.SERVICE.CONTROL after the service is
complete
12.1 SKIP.SERVICE To specify if the service needs to be run or can be skipped. The
two options are YES and NO
13.1 DSC.STATUS No input field which will be updated with values 0, 1, 2 or 3

based on the current status of the service associated with the
field DM.SERVICE.ID
14 DSS.STATUS No input field which will be updated with values 0, 1, 2 or 3

based on the current status of all the services in the
SCHEDULER
15 STATUS.DETAIL No input field which will be updated with some details for
information only
DM.AA.MAPPING
This is the table where the parameters are provided.

The ID for this application must be in the format:

@ID
Id for this application must be in the format:
A 3 digit number followed by an asterisk (*),
followed by a valid user name that must be
present in the USER table.
If only the USER is provided, then the 3 digit
number will be defaulted automatically
1 DESCRIPTION The descriptions of report / interface
2 EXTRACT.TYPE Specifies the task that will be done when the application is verified.
FULL is specified for the entire extract of AA Product and Properties.
The option ‘Only Product’ and ‘Properties’ is reserved for Future Use.
3 VERSION.CHK Has two option Yes or No.
4 PRODUCT.LINE Reserved for future use.
DM.DATA.COMPARE
The Reconciliation extract will be taken from T24 after completion of load as per the process, and the reconciliation
extract from the Legacy will also be extracted and provided in the DATA.IN Directory.
The table is used to compare both the Extracts and to provide the output of the comparison.
@ID
User defined Id.
1 DESCRIPTION The Description for the comparison
2 COMPARE.TYPE
The DM.COMPARE.FIELD.MAPPING table
record which will be used for mapping of the
reconciliation Extracts.
Two comparisons can be performed using
DM.DATA.COMPARE.
1. FILE.COMPARE – file to file compare.
2. ENVIRONMENT.COMPARE - file to
environment compare.
3 ID.POSITION This field position of the Primary key (ID) in the file that is
provided for comparison.
4 FM.DELIM The field delimiter used in the extract files.
5 VM.DELIM The multi value field delimiter used in the extract files.
6 SM.DELIM The sub value field delimiter used in the extract files.
7 HEADER This field is to flag if both the source and target extract for file
compare has Headers or not.
8 LEGACY.FILE.NAME This field is used for information only to store the Legacy Data
Extract.
9 SOURCE.FILE.PATH The directory name where the extract is provided by the Bank.
10 SOURCE.FILE.NAME The file name of the extract provided by the Bank.
11 TARGET.FILE.PATH The Directory Name where the recon extract from T24 is
located.
https://tcsp.temenos.com/R19CD/R19CD.htm#../Subsystems/R19CMUG/Content/CountryPacks/Generic/DataMigrationTool/Template, Fields and D… 10/14

12 TARGET.FILE.NAME The File Name of the recon extract from T24.
13 OUTPUT.FILE.PATH The Output file path where the reconciliation extract is available
after the comparison.
14 OUTPUT.FILE.NAME The Output file name of the reconciliation extract after the
comparison.
15 NO.OF.AGENTS The number of agents that will be required to run the

comparison can be mentioned in this field.
16 APPLICATION.NAME The application name for the comparison.
17.1 FIELD.POSITION This field specifies the position of the field and applicable only
for environment compare.
18.1 SOURCE.FIELD This field specifies the first field of source data file.
DM.EXTRACTOR
Extraction of Data from T24 is necessary when a Migration is to take place between older releases of T24 to a newer
release or for reconciliation extracts.
The application DM.EXTRACTOR is used for extraction of data from T24.
@ID
characters long.
A meaningful ID, indicating the application
name e.g., CUSTOMER should be provided.
CUSTOMER
MM.MONEY.MARKET
LIMIT
1 DESCRIPTION The descriptions of your report set / interface.
2 APPLICATION The name of the table for which the extraction is to be done.
The entry in this field must be present in the
STANDARD.SELECTION.
3 MULTI.COMPANY Whether the extraction is Multi Company or not.
4 FILE.TYPE Specifies the type of file which has to be extracted($NAU or

$HIS or $ARC)
5 OFS.ACTION The value in this field can be either “VALIDATE” or “PROCESS”. If

VALIDATE is selected then the records corresponding to
‘Application’ will be validated for errors and if PROCESS then the
normal extraction is performed.
6.1 SEL.DESC The description of the selection criteria. This is a multivalue

field.
7.1 SEL.FLD The Selection field from the application must be specified here.
This is an associated multivalue field.
8.1 SEL.CRIT The Selection criteria must be specified here. This is an

associated multivalue field.
9.1 SEL.VALUE The Selection Value must be specified here. This is an associated
multivalue field.
10.1 SEL.COMB The Selection Combination must be specified here. This is an

associated multivalue field.
11 SELECT.LIST The save list name must be entered in this field.

12 TARGET.FILE The output filename for the Extraction.
13 OUTPUT.DIR The output directory where the extracted file will reside
14 FM.DELIM The Field Marker that will be used in the extract to separate the
fields.
15 VM.DELIM The Value Marker that will be used in the extract to separate
the Multi values.
16 SM.DELIM The Sub value Marker that will be used in the extract to
separate the Sub values.
17 LOCAL.CCY The Local Currency must be specified only if the extract is done
for DATA.CAPTURE application.
18 DC.TOA.CATEGORY The takeover account category must be specified based on

which the internal account.
19 DC.DAO.START.ID The number from which the department code part in

DATA.CAPTURE id must be started is specified.
20 FILE.HEADER Whether the headers need to be provided for the extract or

not.
21.1 FLD.LABEL The field description for the field to be extracted.
22.1 FLD.APP The application name must be specified from which the for
concurrent extract of the value is done.
23.1 FLD.TYPE The extract type for the field is specified here.
24.1.1 FLD.NAME The field name from the application which is to be extracted.
25.1 TRANS.CONDITION The value in this field can be either “APPEND” or “TRIM” or
“REPLACE”. This field performs the transformation in order to
pick values from other application.
26.1 TRANS.VALUE The value provided depends on the type mentioned in the field
“Trans Condition”. This field becomes mandatory when “Trans
Condition” is provided.
27.1 FLD.RTN A subroutine can be attached to this field that will be used for
different extraction logic.
28.1.1 FLD.APP.FLD The field name from the application mentioned in Fld App must
be specified.
29 DATACAPTURE Whether the extract is done for DATA.CAPTURE application or

not.
30 TRANSACTION.CR The credit transaction code must be specified. The value is

provided only if the extract is done for DATA.CAPTURE.
31 TRANSACTION.DR The debit transaction code must be specified. The value is

provided only if the extract is done for DATA.CAPTURE.
DM.MAPPING.EXTRACT
@ID
Id to this should be valid DMD record id.
1 APPL.NAME The name of the table for which the extraction is to be done. The
entry in this field must be present in the STANDARD.SELECTION.
2 CORE.FLD.NAME The core field name of the application for which the extraction has
to be done
3 SYS.PROG This field indicate what type of core validation check is used for
that particular field
4 FMT This represent maximum number of alpha or alphanumeric or

numeric characters allowed for that particular fields

5 SYS.FLD.NO This field represent the field number of that particular field
6 USR.FLD.NAME The local field name of the application for which the extraction
has to be done
7 USR.SYS.PROG To indicate what type of core validation check is used for that
particular field
8 USR.FLD.NO To indicate what type of core validation check is used for that
particular field
9 USR.FMT No input field which will be updated with values 0, 1, 2 or 3 based

on the current status of the service associated with the field
DM.SERVICE.ID
DM.AA.EXTRACT
@ID
Id to this should be valid user name that must be
present in the USER table.
1 DESCRIPTION The description about the extract is provided.
2 PRODUCT.LINE This field is used specify the product line for which the extract is to
be taken. Only two options are valid either “Deposits” or “Lending”.
3 FM.DELIM To specify field level delimiter.
4 VM.DELIM To specify the delimiter for multi value fields.
5 SM.DELIM To specify the delimiter for sub value fields.
6 OUTPUT.DIR To specify the output directory in which the extract will be placed.
7 EXTRACT.NAME The name in which the extracted file will be created in the
directory.
T24.SAB.INFO
@ID
Id to this should be SYSTEM
1 DAB.INFO.DETAILS This is an no inputtable field
2 SOURCE.SERVER This field is used to specify the source server

name/id
3 COMPANY.ID This field is used to specify the company ID of

the environment
4 SOURCE.SL.ID This field is used to specify the savelist ID. If

the selected application need to be
compared. If not, the build will be crated for
all applications
5 INFO.DATE This field will be automatically updated by

the system after running the service with info
build date
6 INFO.STATUS This field will be automatically updated by

the system after running the service with
status
7 DAB.SOURCE.DETAILS This is an no inputtable field
8 SOURCE.DATE This field will be automatically updated by

build date

9 SOURCE.STATUS This field will be automatically updated by

status
10 DAB.TARGET.DETAILS This is an no inputtable field
11 TARGET.SERVER This field is used to specify the target server

name/id
12 TARGET.DATE This field will be automatically updated by

date
13 TARGET.STATUS This field will be automatically updated by

status
14 DAB.COMPARE.DETAIL This is an no inputtable field
15 REVERSE.COMPARE If the reverse comparison needs to be done

then this is set to Y (i.e, From Target to
Source as well)
16 COMPARE.DATE This field will be automatically updated by

date
17 COMPARE.STATUS This field will be automatically updated by

status
18 OAB.SOURCE.DETAILS This is an no inputtable field
19 OAB.SOURCE.SL.ID This field is to specify the savedlist ID with BP

(Directory) names to create the build
20 OAB.SOURCE.DATE This field will be automatically updated by

build date
21 OAB.SOURCE.STATUS This field will be automatically updated by

status
22 OAB.TARGET.DETAILS This is an no inputtable field
23 OAB.TARGET.SL.ID This field is to specify the savedlist ID with BP

(Directory) names to create the build
24 OAB.TARGET.DATE This field will be automatically updated by

build date
25 OAB.TARGET.STATUS This field will be automatically updated by

status
26 OAB.COMPARE.DETAILS This is an no inputtable field
27 OAB.COMPARE.DATE This field will be automatically updated by

date
28 OAB.COMPARE.STATUS This field will be automatically updated by

status

Published on: 14/05/2019

3) Template, Fields and Description PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

3) Template, Fields and Description PDF

Uploaded by

Copyright:

Available Formats

8/5/2021 Template, Fields and Description

https://tcsp.temenos.com/R19CD/R19CD.htm#../Subsystems/R19CMUG/Content/CountryPacks/Generic/DataMigrationTool/Template, Fields and De… 1/14

Template, Fields and Description

No. Field Name Description

@ID ID must be SYSTEM.

2.1 DESCRIPTION The descriptions of your report set / interface.

5 MNEMONIC Specify the company Mnemonic

10 OVERRIDE Overrides that are generated, if any.

No. Field Name Description

1 APPLICATION The application for which the conversion carried out.

2 SOURCE.DIR The source directory of the data file consisting of Legacy ID is

3 SOURCE.FNAME The Data file name consisting of Legacy ID is given.

https://tcsp.temenos.com/R19CD/R19CD.htm#../Subsystems/R19CMUG/Content/CountryPacks/Generic/DataMigrationTool/Template, Fields and De… 2/14

No. Field Name Description

@ID A 3 digit number followed by an asterisk (*), followed by a

1 DESCRIPTION Free text Description.

3 RESERVED.5 Future Use

5 SELECT.LIST This is an optional filed, where a valid &SAVEDLISTS& name

https://tcsp.temenos.com/R19CD/R19CD.htm#../Subsystems/R19CMUG/Content/CountryPacks/Generic/DataMigrationTool/Template, Fields and De… 3/14

12 RECONCILIATION We need to specify if Reconciliation Folders are to be created

13 RECON.DIR The Directory name must be specified here where the

16 FILE.CONV.REQD File conversion will be done if this field is set to YES.

18 CONVERSION.TYPE Conversion type is specified here. Values entered here are NT

No. Field Name Description

1 DESCRIPTION Free text Description.

3 DMD.NAME DMD Name to be specified.

https://tcsp.temenos.com/R19CD/R19CD.htm#../Subsystems/R19CMUG/Content/CountryPacks/Generic/DataMigrationTool/Template, Fields and De… 4/14

13 FIRST.POSITION This field becomes Mandatory on specifying POSITION in

14 LAST.POSITION This field becomes Mandatory on specifying POSITION in

15 DATAFILE.COUNT The number of records in datafile will be updated here.

No. Field Name Description

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

3 LOAD.TYPE Either ‘OFS’ or ‘WRITE’ or ‘READ.REPLACEMENT’ to specify if the

https://tcsp.temenos.com/R19CD/R19CD.htm#../Subsystems/R19CMUG/Content/CountryPacks/Generic/DataMigrationTool/Template, Fields and De… 5/14

4 OFS.ACTION A value ‘VALIDATE’ or ‘PROCESS’ will just validate/ process the

5 OFS.FUNCTION The following FUNCTIONS are allowed to be specified to be used

6 FILE.TYPE The Type of T24™ files to be updated. Values could be $NAU,

7 OFS.VERSION The T24™ Application’s Version to be used when loading

12 ESC.SEQ.FR When a particular character in the incoming data needs to be

13 ESC.SCR.TO Works in conjunction with ESC.SEQ.FR, this is the character to

https://tcsp.temenos.com/R19CD/R19CD.htm#../Subsystems/R19CMUG/Content/CountryPacks/Generic/DataMigrationTool/Template, Fields and De… 6/14

No. Field Name Description

https://tcsp.temenos.com/R19CD/R19CD.htm#../Subsystems/R19CMUG/Content/CountryPacks/Generic/DataMigrationTool/Template, Fields and De… 7/14

11 DSC.TYPE Dsc type should be either DMD or DME

12 PRE.PROCESS This field is used to run the DM.PRE.PROCESS service as multi-

No. Field Name Description

https://tcsp.temenos.com/R19CD/R19CD.htm#../Subsystems/R19CMUG/Content/CountryPacks/Generic/DataMigrationTool/Template, Fields and De… 8/14

1.1 DESCRIPTION The description of the SCHEDULER.

2 DSS.TYPE To indicate whether the service needs to be run for

3 VERIFICATION.DSS The DM.SERVICE.SCHEDULER table record which needs to be

4 RUN.STATUS To indicate whether the service needs to be started or stopped.

5.1 DM.SERVICE.ID To store the DM.SERVICE.CONTROL table record which needs to

6.1 VERIFICATION To store the DM.SERVICE.CONTROL table record which needs to

11 NO.OF.ERRORS No input field to update the number of records in error from

13.1 DSC.STATUS No input field which will be updated with values 0, 1, 2 or 3

14 DSS.STATUS No input field which will be updated with values 0, 1, 2 or 3

This is the table where the parameters are provided.

No. Field Name Description

https://tcsp.temenos.com/R19CD/R19CD.htm#../Subsystems/R19CMUG/Content/CountryPacks/Generic/DataMigrationTool/Template, Fields and De… 9/14

1 DESCRIPTION The descriptions of report / interface

3 VERSION.CHK Has two option Yes or No.

4 PRODUCT.LINE Reserved for future use.

No. Field Name Description