Static Tlm Usr Guide

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 tab-delimited 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 Other StaticTLM Delimiter O * O *

StaticTLM CalcShortCode3 – when set to ‘Y’, enables more than 1024 accounts to be created.

O ** O ** 1 (Y/N)

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.

O O S 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.


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.



Used by Entry name Mandatory or

Optional Data Type

Max length

Cash Other BANK table (AgentCode parameter as per AGNT)

LocalAccNo M M S 60 CorrAccNo O O I AccountType M M I Currency M O S 3 AccountName (maps into the corr_name field on the bank table)

O O S 60

AccShortName O O S 20 (maps into the short_name field on the bank table). AddressLine1 O O S 40 AddressLine2 O O S 40 AddressLine3 O O S 40 Town O O S 40 State O O S 40 PostCode O O S 10 Country O O S 40 Phone O O S 20 Telex O O S 20 Fax O O S 20 SWIFT O O S 20 Retention O O I ChargeCurrency O O S 3 Investigations (refers to the LocalAccNo of the lead account to use for the definition of investigations parameters)

O O S 60

Categories (refers to the LocalAccNo of the lead account to use for the definition of report parameters)

O O S 60

FinancialLimits (refers to the LocalAccNo of the lead account to use for the definition of financial parameters)

O O S 60

CommsCode O O S 14 maps to the afts_loc (mail box address). SortCode O O S 8 TerritoryCode O O S 8 ChargesContct O O S 60 InterestContct O O S 60 AccDefSource (maps to the section_code on the bank table).

O O S 8

Contact O O S 60 AccountBasis O O I ReportArchive O O I Priority O O I SvblRuns N/A O I

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

AgentCod M M S 60 AgentName O O S 60 AgentShort O O S 20 AgentType O O I

RecFlag O O I

FEED table (message_feed)

FeedShortCode O O S 3 FeedSubAccNo M M S 100 FeedLatestStmtDate O O S 10 FeedLatestStmtNo O O I FeedLatestStmtPg O O I


Used by Entry name Mandatory or Optional

Data Type

Max length

Cash Other FeedRecordBals O O I FeedBalanceType O O I FeedAVAB O O I FeedDescription O O S 60 FeedAliasLocal O O S 100 (FeedAliasNo O O I FeedAliasCode O O S 3 FeedRefmaskLocal O O S 100 (FeedRefmaskNo O O I FeedRefmaskCode O O S 3 FeedCodmaskLocal O O S 100 (FeedCodmaskNo O O I FeedCodmaskCode O O S 3 FeedDefaultSource O O S 8 FeedItemOverDef O O I FeedLoadAdvisory O O I FeedCollectStats O O I FeedStmtFreq O O I FeedStmtSource O O I FeedStmtOrigin O O I FeedStatus O O I FeedCreditLimit O O F FeedClosed O O S 10 FeedReason O O I FeedMLNV M M I FeedPropTime O O S 10 FeedPropTrigger O O I FeedCreateTxn O O I FeedCheckDuplicate O O I FeedDisableHeaders O O I FeedCVAB O O I FeedDebitLimit O O F FeedRefMaskSub O O S 100 FeedAliasSub O O S 100 FeedCodMaskSub O O S 100 FeedValidateBals O O I FeedValidateSeq O O I FeedValueAdjs O O I

BFIN table FinterestNo O O I FinterestCode O O S 3 FcredIntRate O O F FCredIntMethod O O I FDebtIntRate O O F FDebtIntMethod O O I FCredPotentials O O I FNoDebtPotentials O O I FMinDebtIntAmt O O F FMinDebtIntChg O O F FMinCredIntAmt O O F FMinCredIntChg O O F FMaxWrOffAmtLC O O F FMaxWrOffAmtLD O O F FMaxWrOffAmtSC O O F FMaxWrOffAmtSD O O F FMinWrOffAgeLC O O I FMinWrOffAgeLD O O I FMinWrOffAgeSC O O I FMinWrOffAgeSD O O I FChgLimitDebit O O F FChgLimitCredit O O F



Data Type

Max length

Cash Other FOverMinIntDebit O O F FUndMinIntDebit O O F FOverChgLimitDebit O O I FUndChgLimitDebit O O I FOverMinIntCredit O O I FUndMinIntCredit O O I FOverChgLimitCredit O O I FUndChgLimitCredit O O I

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

CHAncillaryCurrency O S 3 CHClosingBalance O F CHCredIntMethod O I CHCredIntRate O F CHDebtIntMethod O I CHDebtIntRate O F CHInterestCode O S 3 CHInterestNo O I CHLatestMsgNo O I CHLatestStmtDate O S 10 CHLatestStmtNo O I CHLatestStmtPg O I CHMissingBalance O F CHMissingCount O I CHOdMethod O I CHSplit O I

GRUP table* GroupCode M M S 12 GroupType O O I GroupDesc O O S 60 GroupLoc O O S 12

Group1Code M M S 12 Group1Type O O I Group1Desc O O S 60 Group1Loc O O S 12










Data Type

Max length

Cash Other Group9Code M M S 12

Group9Type O O I Group9Desc O O S 60 Group9Loc O O S 12











ACGR table*** CorrAccNo M M I USGR table*** UserId M M S 8 STGR table*** SectionCode M M S 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.


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 1

AgentName 2

LocalAccNo 3

AccountName 4

SWIFT 5

AccountType 6

Currency 7

Retention 8

FeedShortCode 9

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: [email protected]

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: [email protected]

Australia and Asia

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

tel: +65 6224 7689 fax: +65 6222 4039 email: [email protected]

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.

Documents

Static Tlm Usr Guide