FEED LOADING

Project Name:

TLM

Owner:

Shweta Kulkarni

Date Created:

14th October 2011

Last Updated By:

Shweta Kulkarni

Date Last Updated

19th October 2011

The document is also distributed to the following for information

Name

Role

Pasupaty, Rajesh X

Project Manager

Albert Shantakumar

Project Lead

Contents:Page no.

1. Introduction

.. 3

2. Example of data feed

.. 4

3. Data feed loading through TLM recon admin

.. 5

4. Data feed loading through Unix-STL fetch engine

. 11

Introduction:Feed loading can be done in both ways : manually and automated. Manually it can
be done by the TLM recon admin & automatically through unix STL fetch engine
or windows fetchit server.
i.e,
Data feed loading can be done in 3 different ways:1. Through TLM recon admin
2. Through UNIX STL fetch engine
3. Through Windows - fetchit server

The first two methods mentioned above are explained in this document.

An example of a data feed is as below:-

Ledger side data feed

SIDE|PAGENO|STMTDATE|FEEDNO|RECCAT|SETTDATE|UNITS|CURREN
CYCODE|TAXDECODE|OMNIACCOUNT|CHASEACCOUNT|OMNITRANSA
CTIONTYPE|SEDOL|ORIGIN|OFST|TRANSACTIONCLASS|SECURITYDESC
RIPTION|TAXCODE|RECENTNUMBER|BATCH
L|1|20110801|ICLedger01|InC|20110731|110|INR|1234|OMNI1234|Chase1234|LE
DGER|L8146F945|334|RPT-|Redemption|Venkat's Security|889|4453|889

Statement side data feed

SIDE|PAGENO|STMTDATE|FEEDNO|RECCAT|SETTDATE|NETAMOUNT|P
RINCIPALAMOUNT|INCOMEAMOUNT|CURRENCYCODE|TRANSACTION
CLASS|TRANSACTIONNUMBER|TRANSACTIONGROUP|TRANSACTIONC
ATEGORY|TRANSACTIONSTATUS|CHASEACCOUNT|WSSACCOUNT|ISIN
|CUSTOMERREFERENCE1|COMMENT|SECURITYDESCRIPTION|POSTED
DATE|PAYABLEDATE
S|1|20110801|ICStatement01|InC|20110731|-300|-400|100|INR|ABC|100002|FX
Sold|PQE|YES|52078|wss_acc|L8146F945|VDA|T|VENKAT's
SECURITY|20110731|20110731

1. Data feed loading through TLM recon admin

The data feed from the unix box is loaded through the TLM recon admin.
Procedure:1. Login to the TLM recon admin with the appropriate login credentials.
2. Go to Servers Validation Insert

3. Mention the path name of the data feed which is present in the unix box in the
File Name tab.
For example: Consider the feed file name as abc.txt in /tmp directory in Unix
box. Then the File Name as in the above screenshot should be: /tmp/abc.txt
4. Select the GEMS engine from the drop down menu in the Program tab.
5. The GEMS Template is the Template of the feed file as defined in the KB.
For example: FD_PBDI is the template defined in KB for DI reconciliation.

6. Click OK. Right click on validation & click on refresh as shown in the below
screenshot.

7. To check whether the file has got loaded successfully or not, login to the Sybase
with the appropriate login credentials.
The FILS table gives the record of each file loaded through GEMS.
The following query can be used:select * from fils order by file_id desc

The MESSAGE_HEADER table gives the header record of the incoming feed.
The following query can be used:select * from message_header where file_id=2215

To check whether the feed is loaded successfully or not, check the load_flag and
status column in the message_header table.
The following values indicate the loading process in the load_flag column:2 Load complete
10 Invalid page, operator intervention
The following values indicate the status in the status column:2 Loaded
13 Missing/Invalid statement header
15 Probable duplicate statement page
37 Statement date in future

An ITEM table shows the details of the items which require reconciliation.
Records with negative corr_acc_no represent data that has loaded unsuccessfully
and is awaiting user maintenance.
The following query can be used:select * from item where corr_acc_no=100001335
or
select * from item where alias_4 in (select message_no from message_header
where file_id =2215)

10

2.Data feed loading through Unix-STL fetch engine

The feed files are loaded through this utility. A configuration file is used by fetch
for file transfers.
In a configuration file:Any line containing a # will be treated as a comment.
All entries must be separated by spaces only.

Pre-requisites for the configuration file:SOURCEDIR=/apps/TLM/datafeeds/waiting (It is the source for the files)
TARGETDIR=/apps/TLM/datafeeds/processed (This is the directory into which
the files should be moved on success)
FAILEDDIR=/apps/TLM/datafeeds/failed (This is the directory into which the
files should be moved on failure)

The other entries configured in the configuration file are:VERSION=TLM

POLLTIME=5 (It specifies how long the program waits (in seconds) before it
checks if the file size has changed. If this is missing it defaults to 1 second)
FILEBLOCK=200 (The number of files that stlfetch processes at a time. If a value
is not input, it defaults to 2000)
PAUSETIME=60 (It specifies how long the program waits (in seconds) between
runs. If it is not set, the value defaults to 300 seconds)

11

An example of the data configured is as below:PBDI PBDI.trg:static FD_PBDI GEMS null

PBDI label
PBDI.trg trigger
FD_PBDI Template as defined in KB
GEMS Engine
:static implies-the trigger row is retained in the LOAD_TRIG table

An entry into the LOAD_TRIG table is made which contains the following
columns: Trigger_name
Datafiles
Load_flag

Below is the screenshot of the LOAD_TRIG table with the respective columns as
seen in Sybase:-

12

For the example taken above,

The trigger_name=PBDI.trg
Datafiles=name of the files where wildcards can also be used (for example: *, ?)
Load_flag= Used by stlfetch to determine if another instance is already processing
this type of file. If the value is zero (0) then the trigger is available for processing.
In the Unix box, copy the feed file to the waiting directory. For example, if the
feed file is di.txt, then the following command can be used:13

cp di.txt /apps/TLM/datafeeds/waiting
This file is then picked up by the STL fetch for processing. To check whether the
file is loaded successfully or not, login to the Sybase and check in the FILS,
MESSAGE_HEADER & ITEM table as explained above.

14