Temenos Store - PACS - AC.DATA - EXTRACT - User Guide
Temenos Store - PACS - AC.DATA - EXTRACT - User Guide
No part of this document may be reproduced or transmitted in any form or by any means,
for any purpose, without the express written permission of TEMENOS HEADQUARTERS SA.
Table of Contents
Document History
Comments:
Tool developed by PACS Accounting team for faster account data extraction.
1. Introduction
This tool is designed for extracting the basic information required for analysing issues on account
balance, statement. The data extracted by this tool are to be attached along with PACS ticket logged for
issue analysis. By this, we can avoid manual work involved in extracting various data.
2. Overview
PACS.AC.DATA.EXTRACT is design as a T24 application with various fields. Based on the field values
supplied the application will extract the below basic details which are required for account balance and
statement related issue analysis.
ACCOUNT.PARAMETER
SPF
INTERCO.PARAMETER
DATES
COMPANY
ACCOUNT
EB.CONTRACT.BALANCES
ACCT.ACTIVITY data
ACCT.STMT.PRINT
ACCOUNT.STATEMENT
GL listing
ENTRY.HOLD validation
We recommend installing this application in production system once after complete testing. Once
the application available in production, it will be available for any test environment and it does not
require installation of the same for each test environment restored.
Step 1:
Create a local BP (ex: PACS.TOOL.BP) & FTP (in ASCII mode) the attached routines namely,
1) I_F.PACS.AC.DATA.EXTRACT
2) PACS.AC.DATA.EXTRACT
3) PACS.AC.DATA.EXTRACT.FIELDS
4) PACS.AC.DATA.EXTRACT.VALIDATE
5) PACS.AC.DATA.EXTRACT.RUN
6) PACS.AC.DATA.EXTRACT.EXEC
7) PACS.AC.DATA.EXTRACT.SUB
o And place the insert file under the I_files.jar stored under temn.tafj.directory.insert
Verify the jshow/tShow output of the routines to ensure all the routines are available as expected.
Step 2:
Step 3:
Now verify the EB.DEV.HELPER record which was created using V function. This step created all the
necessary components like PGM.FILE, STANDARD.SELECTION records.
Step 4:
Restart the App server. This is to ensure the codes are available for all session.
Step 5:
For TAFJ client, we recommend to run this application from Classic. Lower TAFJ release do not support
the launching of Phantom process from Browser.
4. Field Description
ACCOUNT.NUMBER
It is a multi-valued field.
Enter the problematic account number for which data extract needed. If the number of accounts for which
the data extract is needed is small in number, we can multi value this field and give the required account
numbers in each multivalued field.
If the no. of accounts are more and cannot be input each number by multi-value ACCOUNT.NUMBER
field then please create a file with all the required account numbers (sample as shown below)
Recommend to have a directory under bnk.run for TAFC and UD directory for TAFJ runtime.
And incase of multi-app server, ensure the file location is shared or accessible from all server.
We can even use &SAVEDLISTS& as list file path
Note: Accounts to be supplied either ACCOUNT.NUMBER or as List file. Cannot use both.
While using list file, ensure the file was FTP in ASCII mode and ensure there are no spaces at the end of
account number.
LOG.FILE.PATH
ENTRY.START.DATE
An option to supply the date since entries for given accounts are to be extracted. Can be used for
accounts with high volume entries.
If left blank, then all entries would be extracted for the given accounts.
GL.EXTRACT.REQ
This field must be set to YES for extracting EB.SYSTEM.SUMMARY and EB.JOURNAL.SUMMARY
listing.
Default value is NO.
GL.START.DATE
Optional field.
Can supply the date since the GL lists from EB.SYSTEM.SUMMARY and EB.JOURNAL.SUMMARY
table are to be extracted. If not supplied, then GL listing will be extract since beginning.
GL.BRANCH.REQ
Optional multi-value type field to supply the branches for which GL listings are needed. If not supplied,
then GL listing will be extracted for all branches.
WORKING.BAL.CHK
It is a YES/NO field. If this field is given YES, then the ENTRY.HOLD validation will be done for the given
account and all the entry hold records along with the amount present in the ENTRY.HOLD for the given
accounts would be extracted. This is an optional field and defaulted value is NO.
Can be used for incorrect working balance related issues.
FWD.ENT.DETS.REQD
It is a YES/NO field. If this field is set to YES, then the entries from ACCT.ENT.FWD for the required
account will be extracted. This is an optional field with default option NO.
Can be used for issues related to available balance.
DATE.EXPO.REQD
It is a YES/NO field. If this field is given YES, then the future exposure dated entries for the required
accounts would be extracted. This is an optional field with default option NO.
Can be used for issues related to incorrect Cleared balances in account.
CLEAR.LOG.FILES
It is also a YES/NO field. If set to YES, then the present content of log file path will be cleared to extract
the data freshly.
EXECUTION.STATUS
Field to indicate the current status of the tool running. If the tool is run for multiple accounts, then
application record can be opened in view/see mode to check the current status. It will indicate the account
number that was being processed.
The field will become null after processing all accounts.
5. How to use
Kindly ensure that the application PACS.AC.DATA.EXTRACT was installed by following the steps
shown earlier. We recommend installing this application in production system once after
complete testing. Once the application available in production, it will be available for any test
environment and it does not require installation of the same for each test environment restored.
Please follow the below steps to start with the data extraction using this application.
STEP 1:
STEP 2:
Account number is mandatory for running this tool. Account numbers can be manually supplied in the
ACCOUNT.NUMBER field. Can be multivalued for more than one accounts.
STEP 3:
Set the other field values as required. For example, start date for GL extraction, Working Bal Chk. After
supplying all field values commit the record.
STEP 4:
After committing the record, please verify the record. The data extraction begins soon after the record is
verified and the status can be seen in EXECUTION.STATUS field.
STEP 5:
Open the record in See mode to check the status. Field Execution Status will indicate the currently
processing account. The field will be blank upon completion.
STEP 6:
Check the content of Log file path and note the records created with today’s T24 date suffixed.
STEP 7:
FTP the extracts in ASCII mode and attach those data while logging PACS ticket.
6. Recommendations
1. Use this tool for extracting data for analysing account balance related issues and supply the data
extracted while logging the ticket with PACS.
2. Install the tool in production system to avoid installation of the same each time while preparing test
environment.
3. Extract the information from test environment where the information will be static.
4. While supplying account in List file, ensure the file is accessible across all application server in a
multi-app environment
5. Ensure the account numbers are supplied without any space at the end while using list file
6. For TAFJ runtime, use classic for data extraction. Browser functionality is available only with latest
TAFJ service pack.
For TAFJ runtime, ensure the jar file and insert file are place under right location
Disclaimers
As this template will be used for a wide variety of documents, you are advised by the Legal Department
to ensure that you have the correct Temenos disclaimer for your particular document. If you are unsure of
anything please contact the Legal Department.