TLM Reconciliations

StaticTLM User Guide

DISCLAIMER
SmartStream Technologies makes no representations or warranties regarding the contents of this document. We
reserve the right to revise this document or make changes in the specifications of the product described within it at
any time without notice and without obligation to notify any person of such revision or change.
COPYRIGHT NOTICE
2000 -2009 Copyright of SmartStream Technologies. All rights reserved. No part of this publication may be
reproduced, stored in a retrieval system, or transmitted in any form or by any means - electronic, mechanical,
photocopying, recording, or otherwise - without the prior written permission of SmartStream Technologies.
INTELLECTUAL PROPERTY WARNING
The contents of this document and the software it describes are the intellectual property of SmartStream
Technologies. The ideas contained in this document must not be disclosed to any third party.
TRADEMARK NOTICE
TLM is a registered trademark of SmartStream Technologies. All rights reserved.
Other trademarks recognised and property of their respective owner.
DOCUMENT INFORMATION
Doc Ref: 512-1000-00
Edition 1
July 09

Contents iii

Contents
Introduction .......................................................................................... 1
About StaticTLM .......................................................................................................... 1
How is this guide organised? ........................................................................................ 1

Usage Guidelines ................................................................................. 3

Auto load tables ............................................................................................................ 4

Configuring StaticTLM ........................................................................ 5

Configuration file syntax .............................................................................................. 5
Configuration file parameters ....................................................................................... 6
Data mapping guidelines ............................................................................................ 11
Example configuration file ......................................................................................... 11

Running StaticTLM ............................................................................ 13

Potential issues............................................................................................................ 13

Software Support ............................................................................... 15

Calling SmartStream Technologies Support ............................................................... 15
Before you call... ......................................................................................................... 16

Introduction 1

Introduction

This guide describes the StaticTLM utility and how it is used to automatically
load sets of static data into the TLM database.

About StaticTLM
StaticTLM enables you to fully populate the main account static tables from a
CSV input file.
You can also use StaticTLM to overwrite data in the TLM database, or to add to
any existing data, by inserting additional fields into the original CSV file and
reloading.

How is this guide organised?

This guide is divided into the following sections:

usage guidelines provides a list of guidelines which should be considered

before using StaticTLM.

Configuring StaticTLM describes how to setup StaticTLM, including how

to specify the required data mapping in the configuration file.

Running StaticTLM lists the command line parameters required to run the
utility, and a list of potential issues.

Software Support includes contact details for SmartStream Support.

Usage Guidelines 3

Usage Guidelines

Before using StaticTLM to load data, consider the following usage guidelines:
Currency Codes
If StaticTLM is not configured to automatically add unknown currency codes,
you must ensure that you add any currencies specified for cash accounts prior to
loading the account static.
Category codes
If StaticTLM is not configured to automatically add unknown category codes, if
an account is to be added to a category, that category must be present prior to
loading the account static.
Group codes
If StaticTLM is not configured to add unknown group codes, if the account is to
be added to a group, that group must be present prior to loading the account
static.
Lead set data
If you want static data for lead sets to be used and added to the bank and
message feed tables, the lead set details must either be inserted into the load file
as the first rows, to allow later use in the auto load, or manually added prior to
the load.
Data loading order
The static data must be added in the following order:
1.

currency table

2.

agent table

3.

group table

4.

bank, bfin and message_feed tables

5.

acgr table

Bank, bfin and message_feed are loaded as one. If any of the above tables are
not required, for example the group table, they can be omitted.

4 Auto load tables

Auto load tables

You can use StaticTLM to automatically load any of the tables described below.
Table

Online
name

Description

StaticTLM action

AGNT

Categories

A list of
correspondents that
accounts are held
with.

Populates the agent

code as the minimum
allowed.

BANK

Sets

The details of each

separate account held
with correspondents.
This is used in
conjunction with the
Message Feed table.

Depending on the type

of account being
loaded, populates the
basic fields necessary
to save the data.

BFIN

Financial
limits

Financial limits set

for each account.

Defaults to the lead

account used.

MESSAGE_FEED

Message
Feed

The physical account

feed that dictates
whether the data is
from a ledger or
statement, and the
relevant account
number. This is used
in conjunction with
the bank feed.

This data can be

loaded at the same
time as the BANK
records, to which it
must be linked using
the Local_acc_no (the
account name). This
populates the
minimum allowed to
save the data.

CURR

Currency

The various ISO

standard currency
codes that the
accounts are held in.

Populates the currency

code, description and
number of decimal
places. The FX rate is
defaulted to 1.0, the
base currency.

GRUP

Groups

The group codes

loaded to allow the
ACGR table to
function.

Populates the group

code and group type as
the minimum allowed.

ACGR

Groups

Filters used to group

sets into smaller,
workable sets of data.

Populates the group

code and the
corr_acc_no as the
minimum data to save
the record.

Once the tables have loaded, you can check the data contained within them using
the Recon Admin client, or by using SQL select statements.
You can also view a log of the results in the directory specified by the SYST
setting BATCH_LOG_PATH. This log is created each time that you run
StaticTLM.

Configuring StaticTLM 5

Configuring StaticTLM

Before you run StaticTLM, you must first specify the way the data from your
CSVfile is mapped, by adding the required parameter mapping entries to the tabdelimited configuration file.

Configuration file syntax

You can specify the data mapping entry names in the configuration file for most
records as follows:
EntryName <tab>column number

However, for delimiter and file type records, you must instead use the following
syntax:
ParameterName <tab>value

You can find a detailed list of the entry and parameter names available to add to
the configuration file in the next section, Configuration file parameters (p6). You
can also view a sample configuration file on page 11.

6 Configuration file parameters

Configuration file parameters

The parameters and entries that you can add to the configuration file are listed in
the tables below, as well as the entities they are used by, their data type,
maximum length and whether they are optional or mandatory.
The first five entries in the table are parameters mappings used to configure the
behaviour of StaticTLM. The remaining entries are used to specify the field
mappings for the tables in the database.
Used by

Parameter name

Mandatory or
Optional

Data
Type

Max length

Cash
O*

Other
O*

CalcShortCode3 when set to Y,

enables more than 1024 accounts to be
created.

O **

O **

StaticTLM

AddCry controls whether the CURR

table is updated. When set to true, default
values will be inserted into the following
fields in the Curr table:
decimals, (default value of 2)
vabl_date, (default value will be empty)
redenom_code, (default value will be
empty)
redenom_rate (default value will be
empty)
The other fields in this table are updated
with the data from the input file.

5 (TRUE/FALSE)

StaticTLM

AddAgnt - controls whether the AGNT

table gets updated.
When set to true, the fields in this table
are updated with data from the input file.

5 (TRUE/FALSE)

StaticTLM

AddGrp - controls whether the GRUP

table is updated.
When set to true, the fields in this table are
updated with data from the input file.

5 (TRUE/FALSE)

StaticTLM

Delimiter

StaticTLM

1
(Y/N)

Configuring StaticTLM 7

Used by

BANK table
(AgentCode parameter
as per AGNT)

AGNT table
(AddressLine1,
AddressLine2,
AddressLine3,
CommsCode, Contact,
Country, Fax, Phone,
PostCode, SortCode,
State, SWIFT, Telex,
TerritoryCode, Town
parameters as per
BANK)
FEED table
(message_feed)

Entry name

Mandatory or
Optional
Cash
M
O
M
M
O

LocalAccNo
CorrAccNo
AccountType
Currency
AccountName (maps into the corr_name
field on the bank table)
AccShortName
O
(maps into the short_name field on the bank table).
AddressLine1
O
AddressLine2
O
AddressLine3
O
Town
O
State
O
PostCode
O
Country
O
Phone
O
Telex
O
Fax
O
SWIFT
O
Retention
O
ChargeCurrency
O
Investigations (refers to the LocalAccNo of
O
the lead account to use for the definition of
investigations parameters)
Categories (refers to the LocalAccNo of the
O
lead account to use for the definition of
report parameters)
FinancialLimits (refers to the LocalAccNo of O
the lead account to use for the definition of
financial parameters)
CommsCode
O
maps to the afts_loc (mail box address).
SortCode
O
TerritoryCode
O
ChargesContct
O
InterestContct
O
AccDefSource (maps to the section_code on
O
the bank table).
Contact
O
AccountBasis
O
ReportArchive
O
Priority
O
SvblRuns
N/A

Data
Type

Max length

Other
M
O
M
O
O

S
I
I
S
S

60

20

O
O
O
O
O
O
O
O
O
O
O
O
O
O

S
S
S
S
S
S
S
S
S
S
S
I
S
S

40
40
40
40
40
10
40
20
20
20
20
3
60

60

60

14

O
O
O
O
O

S
S
S
S
S

8
8
60
60
8

O
O
O
O
O

S
I
I
I
I

60

60
60
20

AgentCod
AgentName
AgentShort
AgentType

M
O
O
O

M
O
O
O

S
S
S
I

RecFlag

FeedShortCode
FeedSubAccNo
FeedLatestStmtDate
FeedLatestStmtNo
FeedLatestStmtPg

O
M
O
O
O

O
M
O
O
O

S
S
S
I
I

3
60

3
100
10

8 Configuration file parameters

Used by

BFIN table

Entry name

FeedRecordBals
FeedBalanceType
FeedAVAB
FeedDescription
FeedAliasLocal
(FeedAliasNo
FeedAliasCode
FeedRefmaskLocal
(FeedRefmaskNo
FeedRefmaskCode
FeedCodmaskLocal
(FeedCodmaskNo
FeedCodmaskCode
FeedDefaultSource
FeedItemOverDef
FeedLoadAdvisory
FeedCollectStats
FeedStmtFreq
FeedStmtSource
FeedStmtOrigin
FeedStatus
FeedCreditLimit
FeedClosed
FeedReason
FeedMLNV
FeedPropTime
FeedPropTrigger
FeedCreateTxn
FeedCheckDuplicate
FeedDisableHeaders
FeedCVAB
FeedDebitLimit
FeedRefMaskSub
FeedAliasSub
FeedCodMaskSub
FeedValidateBals
FeedValidateSeq
FeedValueAdjs
FinterestNo
FinterestCode
FcredIntRate
FCredIntMethod
FDebtIntRate
FDebtIntMethod
FCredPotentials
FNoDebtPotentials
FMinDebtIntAmt
FMinDebtIntChg
FMinCredIntAmt
FMinCredIntChg
FMaxWrOffAmtLC
FMaxWrOffAmtLD
FMaxWrOffAmtSC
FMaxWrOffAmtSD
FMinWrOffAgeLC
FMinWrOffAgeLD
FMinWrOffAgeSC
FMinWrOffAgeSD
FChgLimitDebit
FChgLimitCredit

Mandatory or
Optional
Cash
O
O
O
O
O
O
O
O
O
O
O
O
O
O
O
O
O
O
O
O
O
O
O
O
M
O
O
O
O
O
O
O
O
O
O
O
O
O
O
O
O
O
O
O
O
O
O
O
O
O
O
O
O
O
O
O
O
O
O
O

Other
O
O
O
O
O
O
O
O
O
O
O
O
O
O
O
O
O
O
O
O
O
O
O
O
M
O
O
O
O
O
O
O
O
O
O
O
O
O
O
O
O
O
O
O
O
O
O
O
O
O
O
O
O
O
O
O
O
O
O
O

Data
Type
I
I
I
S
S
I
S
S
I
S
S
I
S
S
I
I
I
I
I
I
I
F
S
I
I
S
I
I
I
I
I
F
S
S
S
I
I
I
I
S
F
I
F
I
I
I
F
F
F
F
F
F
F
F
I
I
I
I
F
F

Max length

60
100
3
100
3
100
3
8

10

10

100
100
100

Configuring StaticTLM 9

Used by

Currency Header
(CorrAccNo, Currency
parameters as in
BANK, ShortCode as in
FEED)

GRUP table*

Entry name

FOverMinIntDebit
FUndMinIntDebit
FOverChgLimitDebit
FUndChgLimitDebit
FOverMinIntCredit
FUndMinIntCredit
FOverChgLimitCredit
FUndChgLimitCredit
CHAncillaryCurrency
CHClosingBalance
CHCredIntMethod
CHCredIntRate
CHDebtIntMethod
CHDebtIntRate
CHInterestCode
CHInterestNo
CHLatestMsgNo
CHLatestStmtDate
CHLatestStmtNo
CHLatestStmtPg
CHMissingBalance
CHMissingCount
CHOdMethod
CHSplit
GroupCode
GroupType
GroupDesc
GroupLoc
Group1Code
Group1Type
Group1Desc
Group1Loc
Group2Code
Group2Type
Group2Desc
Group2Loc
Group3Code
Group3Type
Group3Desc
Group3Loc
Group4Code
Group4Type
Group4Desc
Group4Loc
Group5Code
Group5Type
Group5Desc
Group5Loc
Group6Code
Group6Type
Group6Desc
Group6Loc
Group7Code
Group7Type
Group7Desc
Group7Loc
Group8Code
Group8Type
Group8Desc
Group8Loc

Mandatory or
Optional
Cash
O
O
O
O
O
O
O
O
O
O
O
O
O
O
O
O
O
O
O
O
O
O
O
O
M
O
O
O
M
O
O
O
M
O
O
O
M
O
O
O
M
O
O
O
M
O
O
O
M
O
O
O
M
O
O
O
M
O
O
O

Other
O
O
O
O
O
O
O
O

M
O
O
O
M
O
O
O
M
O
O
O
M
O
O
O
M
O
O
O
M
O
O
O
M
O
O
O
M
O
O
O
M
O
O
O

Data
Type
F
F
I
I
I
I
I
I
S
F
I
F
I
F
S
I
I
S
I
I
F
I
I
I
S
I
S
S
S
I
S
S
S
I
S
S
S
I
S
S
S
I
S
S
S
I
S
S
S
I
S
S
S
I
S
S
S
I
S
S

Max length

10

12
60
12
12
60
12
12
60
12
12
60
12
12
60
12
12
60
12
12
60
12
12
60
12
12
60
12

10 Configuration file parameters

Used by

ACGR table***
USGR table***
STGR table***

Entry name

Group9Code
Group9Type
Group9Desc
Group9Loc
Group10Code
Group10Type
Group10Desc
Group10Loc
Group11Code
Group11Type
Group11Desc
Group11Loc
Group12Code
Group12Type
Group12Desc
Group12Loc
Group13Code
Group13Type
Group13Desc
Group13Loc
Group14Code
Group14Type
Group14Desc
Group14Loc
Group15Code
Group15Type
Group15Desc
Group15Loc
Group16Code
Group16Type
Group16Desc
Group16Loc
Group17Code
Group17Type
Group17Desc
Group17Loc
Group18Code
Group18Type
Group18Desc
Group18Loc
Group19Code
Group19Type
Group19Desc
Group19Loc
CorrAccNo
UserId
SectionCode

Mandatory or
Optional
Cash
M
O
O
O
M
O
O
O
M
O
O
O
M
O
O
O
M
O
O
O
M
O
O
O
M
O
O
O
M
O
O
O
M
O
O
O
M
O
O
O
M
O
O
O
M
M
M

Other
M
O
O
O
M
O
O
O
M
O
O
O
M
O
O
O
M
O
O
O
M
O
O
O
M
O
O
O
M
O
O
O
M
O
O
O
M
O
O
O
M
O
O
O
M
M
M

Data
Type
S
I
S
S
S
I
S
S
S
I
S
S
S
I
S
S
S
I
S
S
S
I
S
S
S
I
S
S
S
I
S
S
S
I
S
S
S
I
S
S
S
I
S
S
I
S
S

Max length

12
60
12
12
60
12
12
60
12
12
60
12
12
60
12
12
60
12
12
60
12
12
60
12
12
60
12
12
60
12
12
60
12
8
8

Notes
* Defaults to ,.
** Defaults to 0. Overwritten by the [-x[0 or 1] command line parameter, where
specified
*** Specified fields are mandatory only if group data appear in the data file.

Configuring StaticTLM 11

Data mapping guidelines

The following notes provide guidance on specifying certain parameter names in
your configuration file:

When a new feed is being inserted for a Cash account, an associated

currency header record is also inserted.

Sub-account short codes may not be changed once loaded since

short_code is a foreign key on many other tables including Item.

Where the lead parameter is a sub-account, such as for interest rates, the
sub-account number itself should be used explicitly as the parameter
rather than implicitly by using the associated combination of the
reconciliation account number and feed short code.

Lead accounts must either already exist on the database, or appear in

the input CSV file ahead of any account pointing to them. Accounts
being pointed at by the three main lead parameters on the Bank table
might not themselves point to other accounts. Accounts which are being
pointed at by the Bank financial_parm field must have their own Bfin
records.

Once loaded, sub-account short codes might not be changed, since

short_code is a foreign key on many other tables including Item.

Example configuration file

The following example illustrates a typical configuration file:
delimiter

AgentCode

AgentName

LocalAccNo

AccountName

SWIFT

AccountType

Currency

Retention

FeedShortCode

FeedMLNV

10

FeedSubAccNo

11

FeedDefaultSource

12

FeedValidateBals

13

FeedValidateSeq

14

FeedLoadAdvisory

15

FeedPropTime

01/01/2000 00:00:00

FeedCreateTxn

16

FeedCheckDuplicate

17

FeedAVAB

18

GroupCode

19

GroupType

20

Running StaticTLM 13

Running StaticTLM

You run StaticTLM from the command line, using the set of command line
parameters provided.
When the data load starts, if key values already exist in the bank, message_feed,
agnt, bfin or currency_header tables, then the relevant rows will be updated.
However, if the key values are not present, then new data or where appropriate,
data for other tables will be inserted.
Before running StaticTLM you must ensure that any title rows and column
headers have been deleted from your CSV file.
To run StaticTLM

Open a command prompt and enter the following command:

staticTLM <config file> <input file> <servername> <database> [x[0 or 1] [-gDELETE] < <unpw>

where:

<config file> is the configuration file containing the field-to-column

relationships.

<input file> is the delimited data file.

<servername> is the server name.

<database> is the database name.

[-x[0 or 1] is an optional parameter used to control the format of new

sub-account short codes generated by the loader.

[-gDELETE] is an optional parameter that when specified, deletes the

contents of any groups that are named in the feed, before the new data is
inserted. This prevents orphan entries being left in groups even though
their parent records such as Bank, for entries in account groups, have
been removed. It also provides the facility for entries to be removed
from groups and for new groups to be created.
Where an existing group is specified, the group parameters are checked
for consistency with those supplied, and the group will only be updated
if a match occurs.

<unpw> is the name of the file containing your user name and password
on separate lines.

Potential issues
If you experience data mapping issues with the source / bran code when running
StaticTLM, this could be because the source code entry is missing from the dcod
table. This entry must be present for the data to update.
You can use the following sql to check the database for the source code on the
dcod table:

14 Potential issues

select count(*)
from dcod
where codec = <<input source/bran_code>>;

If this entry is missing, you must add it to the table for the data to map.

Software Support 15

Software Support

More information about SmartStream Technologies software can be found in the

other documentation supplied with the product. If you are unable to find the
answer to your question in any of these resources, contact SmartStream
Technologies Support. Details are given below.

Calling SmartStream Technologies Support

Before you call, you should consult the checklist given below, to ensure that you
have all relevant information to hand.
Area

Postal Address

Contact Details

Europe

SmartStream
Technologies Ltd
1690 Park Ave
Aztec West
Almondsbury
Bristol, BS32 4RA
UK

tel: +44 (0) 1454 888485

fax: +44 (0) 1454 888486
email: ssrsup.uk@smartstreamstp.com

North and South

America

SmartStream
Technologies Ltd
61 Broadway
Suite 2824
New York
NY 10006
USA

tel: +1 212 763 6505

tel (US internal): 877 215 8227
fax: +1 212 763 6501
email: ssrsup.usa@smartstreamstp.com

Australia and Asia

SmartStream
Technologies Ltd
70 Anson Road
26-01, Apex Tower
Singapore
079905

tel: +65 6224 7689

fax: +65 6222 4039
email: ssrsup.sea@smartstreamstp.com

16 Before you call...

Before you call...

You will be
asked...

Notes

Your name and

your company
name

You must have already been registered with SmartStream

Technologies Support Desk by your main support contact, otherwise
the call will not be accepted

Software type:
test or
production?

If this is a test issue, it will be treated as a chargeable call unless a

software bug is proven.

Software
version number

Can be found by selecting Help > About from the software menu.

RDBMS Type
& Version

Confirm RDBMS Type (Sybase/Oracle/SQLServer) and Version.

Server
Operating
System Type
& Version

Confirm operating system (UNIX or Windows) and Version.

Priority of call
(1 to 4)

Based on business criticality.

1 Unable to process any transactions.
2 Partially inoperable transactions restricted
3 Operational but functionally impaired
4 Cosmetic problem or enquiry

Full description
of problem
being
experienced

Please provide as much detail as possible Any supporting screen

shots, reports or server logs that may help identify your problem
This information should be sent to your nearest support centre as
listed above. Please ensure that the Heat call reference that you will
be provided with is clearly indicated on any emails and faxes.

Can you
reproduce the
problem?

Yes or No.

Has this
problem
occurred
before?

Yes or No.

Customer Call
ref. (optional)

Please provide us with your own call reference if you have one.