Finacle Application End of Day and Begin of Day Process

(Core Banking System: CBS)

บริษัท ยิบอินซอย จำกัด

523 Mahaprutharam Rd., Bangrak,
Bangkok 10500, Thailand
Tel: 0-2353-8600 Fax: 0-2353-8680

Preface

Finacle Application End of Day Page 1 of 42 Author : Kittichok Chaisaksriskul

and Begin of Day Process Copyright © YIP IN TSOI & CO., LTD. Created Date : July 29, 2014

COMMERCIAL-IN-CONFIDENCE
Purpose of this document
To discuss about processes during End of Day and Begin of Day process including all the standard
actions happening during each EOD/BOD step but will not be including the user defined batch jobs

Intended audience
GHB users

Document History
Version Date Author Comments

1 29-Jul-2014 Kittichok Chaisaksriskul Final

Glossary
Term Definition

ABH After Business Hours

CSOLOP Closure of SOL Operations

CEOD Central End of Day

CBOD Central Beginning of Day

ISOLOP Initiate Service Outlet Operations

SOLVAL SOL Validation

TOD Temporary Overdraft

FFD Flexi Fixed Deposit

SI Standard Instruction

Contents

Finacle Application End of Day Page 2 of 42 Author : Kittichok Chaisaksriskul

and Begin of Day Process Copyright © YIP IN TSOI & CO., LTD. Created Date : July 29, 2014

COMMERCIAL-IN-CONFIDENCE
 Purpose of this document..............................................................................................2
1. Overview.....................................................................................................................4
2. ABH – After Business Hours:.......................................................................................6
3. CSOLOP – Closure of SOL Operations.........................................................................9
4. CEOD – CENTRAL END OF DAY..................................................................................11
4.1 CEOD’s Step by Step process flow..........................................................................13
5. CBOD – Central Beginning of Day.............................................................................20
5.1 CBOD’s Step by Step process flow.........................................................................20
6. ISOLOP – Initiate Service Outlet Operations.............................................................33
7. Other related processes............................................................................................34
7.1 Reinitiating transfer of history transactions – METOH..........................................34
7.2 Verify previous day’s transactions – PTV...............................................................35
7.3 Changing User’s Context SOL – HCCS.....................................................................36
8. Related tables...........................................................................................................36
9. Related menu options...............................................................................................37
10. Key points to be noted..............................................................................................37
11. Some common issues faced during EOD/BOD and there resolutions......................39
12. Flashback...................................................................................................................42

1. Overview

End-of-day & begin-of-day are operations performed in Finacle to mark the logical end-of-
day for a branch level operation and mark the beginning of next working day.

Finacle Application End of Day Page 3 of 42 Author : Kittichok Chaisaksriskul

and Begin of Day Process Copyright © YIP IN TSOI & CO., LTD. Created Date : July 29, 2014

COMMERCIAL-IN-CONFIDENCE
 As part of a bank’s routine functions it is necessary that certain jobs be carried out at the
start of every working day and certain others at the end of every working day. These are
commonly referred to as BOD (Beginning of Day) and EOD (End of Day) processes.

Process Diagram:

SOLVAL and SOLSTAT are independent process and can be run at any time.

SOLSTAT: It shows the status of the Service Outlet.

SOLVAL : Validation of Service Outlet. Below are few validations carried in SOLVAL.

• Unposted Transactions                                               

• Unbalanced transactions initiated by you                            

• Transaction on unverified A/c's                                      

Finacle Application End of Day Page 4 of 42 Author : Kittichok Chaisaksriskul

and Begin of Day Process Copyright © YIP IN TSOI & CO., LTD. Created Date : July 29, 2014

COMMERCIAL-IN-CONFIDENCE
 • Unreconciled Intersol Transaction List                              

• ISO Transactions on us not created                                  

• Outward Clearing Zones open                                         

• Inward Clearing Zones open                                           

• Unverified Inv. Transactions List                                   

• SI's pending execution            

• Unprinted Deposit receipts                                          

• EOD min/max check for Accounts.                                      

• Pending Work Flow Transactions List                                  

• Unverified Proxy Transactions List                                  

• Outstanding Proxy Transactions List                                 

• Pending Purchase and Sale                                            

• Pending Profit and Loss                                             

• Unprocessed External Trans                                          

• Currencies with Non Zero Balance

• Pending Referral Transactions                            

2. ABH – After Business Hours:

ABH is optional process. ABH runs internally on invoking of CSOLOP.

Below are the process happens during ABH.

Finacle Application End of Day Page 5 of 42 Author : Kittichok Chaisaksriskul

and Begin of Day Process Copyright © YIP IN TSOI & CO., LTD. Created Date : July 29, 2014

COMMERCIAL-IN-CONFIDENCE
 Pre- Requisites:

If one user invokes this option, another user cannot perform the same function. The ABH
process must be completed by the same user. However, for some reason if a different user must
continue the process, the first user must be log out from the database.

Activities:

 Marking TOD as expired

 Automatic regularization of TODs

 Interest Calculation on TODs ( if applicable)

 Auto FFD opening

 Transfer of Funds from FFD deposits to Operative accounts

 Auto Closure of deposits

 Auto Verification of Deposits

 Automatic renewal of matured deposits

 Batch Job Executioner

 Standing Instruction Execution

 Site Specific Scripts

STEPS AND PROCESS:

 User exit for ABH : baoe3231.cxx

 ABH calls babx4457 for processing.

 Upon starting ABH db_stat_code is updated as A

 Calls generalABHCheck.scr and gives error/exception if any check fails.

 Calls abh.b2k script

 Db_stat_code at the end of ABH : B

 Db_int_stat_code at the end of ABH : ZZ

Finacle Application End of Day Page 6 of 42 Author : Kittichok Chaisaksriskul

and Begin of Day Process Copyright © YIP IN TSOI & CO., LTD. Created Date : July 29, 2014

COMMERCIAL-IN-CONFIDENCE
 Step No Description Exe name
1 Updating TOD information Babx4015

2 Automatic FFD opening Babx4007

3 Auto regularization of TODs Babx4016

4 Closure of regularized FFDs Babx4008

5 Automatic verification of matured deposits Babx4465

6 User defined batch jobs Babx4009

7 Executing standing instructions Sibx4003

8 Executing site specific scripts abh.site

1. Updating TOD status information such as number of TOD utilized by the customer, TOD amount,
whether TOD is regularized, etc..,

TOD - Temporary Overdraft:

Temporary Overdraft is a facility provided by the Bank to its customers when there is a
shortfall in the customer's account. This facility can be provided to maintain balance restrictions or
loan interest debit / Standing Instructions.

2. Automatic FFD opening :

FFD (Flexi Fixed Deposit) is generally linked to an operative account and is funded when the
balance in the operative account is surplus; Similarly amount from the fixed deposit is transferred back
to the operative account as per requirement. This is also called as sweep-in and sweep-out.

This happens according to the FFD set up provided in data center maintenance menu and
scheme set up.

3. Automatic regularization of TOD:

Finacle Application End of Day Page 7 of 42 Author : Kittichok Chaisaksriskul

and Begin of Day Process Copyright © YIP IN TSOI & CO., LTD. Created Date : July 29, 2014

COMMERCIAL-IN-CONFIDENCE
 This step checks the value of TOD interest level flag and regularizes the TOD amount based on the
deposits made by the account holder and calculates TOD interest if applicable. The TODs with a higher
rate of interest are regularized first when funds are available, to give benefit to the customer.

4. Closure of regularized FFD:

The FFD status is updated as closed after it is regularized as per the scheme level setting or when
the term of FFD is expired.

5. Automatic verification of Matured term deposits

6. User defined jobs

7. Executing Standing Instructions

The Standing Instruction (SI) is a facility provided by banks to account holders who want to make
payments or remittances of a recurring nature like payment of insurance premiums, subscriptions,
transfer of funds, installments to deposit or loan accounts and so on. Customers may give Standing
Instructions to the bank to make these payments or remittances on their behalf on specified dates,

For specified amounts or when the account satisfies certain conditions specified by the account
holder.

8. Executing Site specific scripts

Error Messages:

The Error messages or progress information can be checked from $TBA_TRACE_DIR/log/[SOLID]_ABH.log

The Messages are also sent to the Op Console with the service name ABH_[solid]_PROGRESS

Finacle Application End of Day Page 8 of 42 Author : Kittichok Chaisaksriskul

and Begin of Day Process Copyright © YIP IN TSOI & CO., LTD. Created Date : July 29, 2014

COMMERCIAL-IN-CONFIDENCE
 3. CSOLOP – Closure of SOL Operations

The Closing of SOL Operations is the second step in the EOD and BOD process run by the user at
the Service Outlet at the end of each working day. This closes the operations of the SOL. CSOLOP will
execute ABH if the same is not complete for the SOL.

Pre- requisite:

No user is allowed to carry out any transaction, financial or non-financial, during and after
running Closing of SOL Operations for the service outlet. All the errors and exceptions for the financial
transactions initiated by the service outlet are checked.

Activities:

 CSOLOP executes ABH if already not done

 Execute User defined batch jobs

 Calculate SI Charges

 Carry Forward List for SI

 Execution of Site Specific Scripts

STEPS AND PROCESS:

 User exit for CSOLOP is : baoe3233.cxx

 Displays the status of the sols in the set.

Finacle Application End of Day Page 9 of 42 Author : Kittichok Chaisaksriskul

and Begin of Day Process Copyright © YIP IN TSOI & CO., LTD. Created Date : July 29, 2014

COMMERCIAL-IN-CONFIDENCE
  If generalABHCheck.scr is present this script is called for exception/error checking. (This script will
be called only through ABH. If CSOLOP is invoked directly then this script will not be called)

 Checks if CSOLOP is completed for the list of sols in setid (db_stat_code field of SOL table is
checked)

 Gives an error if CSOLOP is completed or CSOLOP is already running for sols.

 If no errors are there then allows user to press commit.

 Again checks if there are sols ineligible in set for CSOLOP.

 Exe for CSOLOP : babx4458

 Babx4458 internally makes a call to csolop.b2k

 If the script returns success db_stat_code is updated for the SOL.

 Starts at step no 100

 Db_stat_code at the end of CSOLOP is G and db_int_stat_code is ZZZ

Step No Description Exe name

100 Executing user defined batch jobs babx4009

101 Generating carry forward list of Sis sibx4005

102 Calculating SI charges sibx4004

103 Executing site specific script csolop.site

100 – User defined batch jobs

101 – Generating Carry Forward list of Standing Instructions

Standing instructions which have failed to get executed (due to multiple reasons such as
insufficient funds, not satisfying criteria provided by customer) , would be moved to a carry forward
list during CSOLOP based on the flag set up at standing instruction level

All records which are in this list would be tried for execution the next day; if the execution is
successful then the record is deleted from the list.

Finacle Application End of Day Page 10 of 42 Author : Kittichok Chaisaksriskul

and Begin of Day Process Copyright © YIP IN TSOI & CO., LTD. Created Date : July 29, 2014

COMMERCIAL-IN-CONFIDENCE
 102 – Calculating Standing Instruction Charges

SI Execution – Batch Charges collected multiple times whenever Standing Instruction

execution occurs

SI Failure – Batch Charges collected multiple times whenever Standing Instruction failure
occurs

Based on the charge set up, calculation is done for the above two scenarios and collected. If
balance is not available in customer account, a TOD is created.

103 – Executing site specific script (if any)

Error Messages:

The Error messages or progress information can be checked from $TBA_TRACE_DIR/log/[SOLID]_CSOLOP.log

The messages are also sent to the Op Console with the service name CSOLOP_[solid]_PROGRESS

4. CEOD – CENTRAL END OF DAY

The Central EOD is a process carried out at the end of each working day. Before initiating this
process, all the SOL in the data center should have completed their CSOLOP. Central EOD will not
increment the BOD date of any Service Outlet. Once central EOD is started, Inter-Service Outlet and
financial transactions are not allowed.

Pre-requisites:

Jobs that create financial transactions are not to be run during Central EOD

Activities:

 Before CEOD begins the db_stat_code must be “G” i.e. CSOLOP completed for sols in SOL table.

 Runs the PRE_CEOD.site script before executing CEOD. This is a customized script and not a
mandatory one. Bank specific conditions can be checked.

 No user should be logged on while invoking CEOD other than the one who invokes it.
Finacle Application End of Day Page 11 of 42 Author : Kittichok Chaisaksriskul
and Begin of Day Process Copyright © YIP IN TSOI & CO., LTD. Created Date : July 29, 2014

COMMERCIAL-IN-CONFIDENCE
 STEPS AND PROCESS:

 User Exit : baoe3236.cxx

 CSOLOP should be for all SOLs completed for CEOD to start.

 db_stat_code=“E”, db_int_stat_code=“100”

 Runs the PRE_CEOD.site script before executing CEOD.

 This is a customized script and not a mandatory one.

 CEOD will not proceed in case

• More than one users are logged on

• Batch jobs are running

 If any users of batch jobs are running they will have to be sacked.

 Check for table space availability using tblspcchk.sql script in INFENG/sql

 Gives error if any of the table spaces has < 15% space left.

 Following checks are carried out

• All transactions are posted

• All transactions are balanced

 If all checks are success starts the CEOD process.

Finacle Application End of Day Page 12 of 42 Author : Kittichok Chaisaksriskul

and Begin of Day Process Copyright © YIP IN TSOI & CO., LTD. Created Date : July 29, 2014

COMMERCIAL-IN-CONFIDENCE
 4.1 CEOD’s Step by Step process flow

1. Entries just Before CEOD

Before Start of CEOD’s preprocessing function below will be the value of the
db_stat_code field in SOL.

DB_STAT_CODE Description

G CSOLOPCOMPLETED

Also, the value of db_stat_code would change from G to E and the db_init_stat_code
would be null indicating that CEOD is not started yet.

DB_STAT_CODE DB_INIT_STAT_CODE

E “”

/* “” indicates that CEOD is not started yet */

2. Call Inter Sol Tran

The ISO transactions reconciliation is done. The db_stat_code of all sols is updated to
E and the db_init_stat_code would be updated to “0”.

DB_STAT_CODE DB_INIT_STAT_CODE

E 0

/* 0 indicates that CALLINTERSOLTRAN*/

Finacle Application End of Day Page 13 of 42 Author : Kittichok Chaisaksriskul

and Begin of Day Process Copyright © YIP IN TSOI & CO., LTD. Created Date : July 29, 2014

COMMERCIAL-IN-CONFIDENCE
 Inter SOL transactions:

The Inter-SOL transactions, which have occurred for the day would be reconciled or
squared off during this step. Reconciliation of Inter SOL accounts process is called in CEOD
processes automatically. Because of the volume of ISO transactions and to avoid delay during
EOD/BOD processes, if the user wants to reconcile, he can invoke RIST and reconcile the
transactions even before running ABH process.

3. CEOD ATM Jobs

In this process the uniserver is stopped and Finacle is taken offline. All ATM
transactions will be routed to CSIS. Calls daily_down_uniserver.com to bring down uniserver
services.The db_stat_code would be E and the db_init_stat_code would be updated to 1.

DB_STAT_CODE DB_INIT_STAT_CODE

E 1

/* 1- indicates that CALLCEODATMJOBS*/

On opconsole you would get the message “X33 CEOD:Uniserver status update in
progress…”

In case of a failure, “Uniserver status updation failed” .

Finacle Application End of Day Page 14 of 42 Author : Kittichok Chaisaksriskul

and Begin of Day Process Copyright © YIP IN TSOI & CO., LTD. Created Date : July 29, 2014

COMMERCIAL-IN-CONFIDENCE
 4. Contra FinCron Jobs

In this process, the jobs for contra posting are run.Offline_posting.com file is called for
CDCI transactions.the db_stat_code would be E and the db_init_stat_code would be 2.

DB_STAT_CODE DB_INIT_STAT_CODE

E 2

/* 2- indicates that CALLCONTRAFINCRON*/

The services under fincron_type service type are non-listening services that create
contra-entries for the ATM Cash withdrawal transactions.

Message at opconsole “BRN Executing Offline Posting Job (Fincron Job)....”

5. Exception checking

In this stage Exception checking for un- posted and unbalanced transactions are done.

The db_stat_code would be E and the db_init_stat_code would be “3”.

DB_STAT_CODE DB_INIT_STAT_CODE

E 3

/* 3- indicates that CALLCEODEXCEPTIONS*/

The message code at opconsole would be “X34 Exception checks in progress...”

In case there is any failure, then message at opconsole would be “W03 EOD exception
checks failed”

Finacle Application End of Day Page 15 of 42 Author : Kittichok Chaisaksriskul

and Begin of Day Process Copyright © YIP IN TSOI & CO., LTD. Created Date : July 29, 2014

COMMERCIAL-IN-CONFIDENCE
 6. CEOD Tran Jobs

Runs transaction creating batch jobs from BJS table. Call user defined batch jobs which
create transactions.In soleod.com only batch jobs which do not create transactions are
called. The db_stat_code would be “E” and the db_init_stat_code would be “4”.

DB_STAT_CODE DB_INIT_STAT_CODE

E 4

/* 4- indicates that CALLCEODTRANBJS*/

Message at opconsole “ASG Executing batch jobs which create transactions..”

In case of a failure the message at opconsole would be “ASI Transaction creating batch
job failed”.

7. Force Post Tran

Calls babx4049 which proxy posts unposted transactions, if normal posting does not
go through. In this stage the db_stat_code is E and db_init_stat_code would be 6.

DB_STAT_CODE DB_INIT_STAT_CODE

E 6

/* 6- indicates that CALLFORCEPOSTTRAN*/

Display the message at opconsole “ASH Executing Proxy posting of unposted

transactions”

In case of a failure message would be “ASJ Could not post unposted transactions”

Finacle Application End of Day Page 16 of 42 Author : Kittichok Chaisaksriskul

and Begin of Day Process Copyright © YIP IN TSOI & CO., LTD. Created Date : July 29, 2014

COMMERCIAL-IN-CONFIDENCE
 8. EOD Message to SIS

exec_handovermon.com - SIS handover. This is to inform SIS that Finacle is going to go

down as CEOD is happening. During this the db_stat_code would be E and the
db_init_stat_code would be “8”.

DB_STAT_CODE DB_INIT_STAT_CODE

E 8

/* 8- indicates that CALL_EOD_MESGTOSIS*/

The message at opconsole would be “BOA Starting EOD Finacle@Branch handover ...”

9. Call Inter Sol transactions again

Call ISO transactions reconciliation job again. The db_stat_code would be “E” and the
db_init_stat_code would be “5”.

DB_STAT_CODE DB_INIT_STAT_CODE

E 5

/* 5- indicates that CALLINTERSOLTRANAGAIN*/

The message at opconsole would be “ASU Reconciling Intersol Transactions”.

Kindly note, there is no E7 because the GL update process has been clubbed with
EAB/GST update.

Finacle Application End of Day Page 17 of 42 Author : Kittichok Chaisaksriskul

and Begin of Day Process Copyright © YIP IN TSOI & CO., LTD. Created Date : July 29, 2014

COMMERCIAL-IN-CONFIDENCE
 10.EAB/GST update

During EOD/BOD, EAB GST update service if GST Gen on Value Date in HSCFM menu is
set to 'Y' , then system will insert records in GSVT table. GSVT table stores GL sub head
balances value date-wise

When the "GL Sub Head Value dated flag" is set to 'Y', then during EAB/GST update
system will also update 'GL Sub Head Balance' based on the value date along with that of
transaction date. Else, when it is 'N', system will only update 'GL Sub Head Balance' based on
the transaction date.

Beginning of the Day GST update for the SOLS that have marked holidays between
EOD date and the next working date.

BOD GST updates will be done for those SOLS that have marked been holidays before
the next working date. This will insert records into GST for the holidays.

CBS generates an error in case if the credit and debit do not match on transaction
date.

- Exe name: Babx4070

DB_STAT_CODE DB_INIT_STAT_CODE

E 100

11.User defined batch jobs

- Exe name: Babx4009

DB_STAT_CODE DB_INIT_STAT_CODE

E 101

Finacle Application End of Day Page 18 of 42 Author : Kittichok Chaisaksriskul

and Begin of Day Process Copyright © YIP IN TSOI & CO., LTD. Created Date : July 29, 2014

COMMERCIAL-IN-CONFIDENCE
 12.Executing site specific script

- Exe name: Babx4453

DB_STAT_CODE DB_INIT_STAT_CODE

E 102

13.Last CEOD Job

DB_STAT_CODE DB_INIT_STAT_CODE

E ZZZ

 Upon successful completion of all the above steps ceod.b2k script is called.

 At this stage following exceptions are checked

• iso_bal_check_excp_code – Check for ISO balances if zero for all currency

• ac_bal_not_zero_excp_code – Check if sum of acct bal if zero for all currency.

• eod_max_bal_excp_code – If Any account above max balance.

• eod_min_bal_excp_code – If any account below min balance

 Db_stat_code after CEOD is completed is H, Db_int_stat_code after ceod completed is 999

Error Messages:

The error messages or progress information can be checked from $TBA_TRACE_DIR/log/[SOLID]_CEOD.log

The Messages are also sent to the Op Console with the service name CEOD_[solid]_PROGRESS.

Finacle Application End of Day Page 19 of 42 Author : Kittichok Chaisaksriskul

and Begin of Day Process Copyright © YIP IN TSOI & CO., LTD. Created Date : July 29, 2014

COMMERCIAL-IN-CONFIDENCE
 5. CBOD – Central Beginning of Day

Central BOD is a process carried out at the beginning of each working day. It can be run at the
Central user, service outlet or the data center level. After running Central BOD, the BOD dates of all the
service outlets in the Set are incremented.

5.1 CBOD’s Step by Step process flow

1. Entries just Before CBOD

Before Start of CBOD’s preprocessing function below will be the value of the STATUS
field in EST. Kindly note EST table is abbreviation for EOD STATUS TABLE that contains last
successful status of ETD to HTD data transfer.

DB_STAT_CODE EST STATUS

H CBOD completed successfully.

/* H- indicates CENTRALEODCOMPLETED */

2. Change of Date

To indicate to system that BOD is starting all SOL are updated with value K for
DB_STAT_CODE and 1 for DB_INIT_STAT_CODE

DB_STAT_CODE DB_INIT_STAT_CODE

K 1

/* K – indicates CENTRALBODSTARTED */
/* 1 – indicates CALLCBODDATECHANGE */

Also we get this message in screen “X40 BOD date change in progress...” in K1

During the process the date change happens in GCT (db_stat_date) and SOL
(bod_sys_date) tables post which the LGI tables BOD date (bod_date) is also modified.
Finacle Application End of Day Page 20 of 42 Author : Kittichok Chaisaksriskul
and Begin of Day Process Copyright © YIP IN TSOI & CO., LTD. Created Date : July 29, 2014

COMMERCIAL-IN-CONFIDENCE
 3. Bring up UNISERVER

DB_STAT_CODE DB_INIT_STAT_CODE

K 6

/* K – indicates CENTRALBODSTARTED */
/* 6 – indicates UP_UNISERVER */

On console you will get the message as “BPD Bringing up Uniserver and Refresh
servers as part of BOD ...”

Searches for PATH of daily_up_uniser.com and calls the same by passing the os user id
based on the modules.dat entry for CDCI (CDCI is UPR user id)

In case of failure it will show the message “BPE Bringing up Uniserver and Refresh
servers as part of BOD failed”

4. DTD Purge

DB_STAT_CODE DB_INIT_STAT_CODE

K 3

/* K – indicates CENTRALBODSTARTED */
/* 3 – indicates CALLCBODDTDPURGE */

You will have this message in console “X42 BOD DTD purge in progress...”

Finacle Application End of Day Page 21 of 42 Author : Kittichok Chaisaksriskul

and Begin of Day Process Copyright © YIP IN TSOI & CO., LTD. Created Date : July 29, 2014

COMMERCIAL-IN-CONFIDENCE
 4.1 DTD Purge: Step 1

As a part of this step a set of SQL and DAT files will be generated for the DTD table

bash->ls *.sql *.dat

DAILY_TRAN_DETAIL_TABLE.sql /* create table for DTD */

DAILY_TRAN_DETAIL_TABLE_idx_rename.sql /* rename DTD to ETD */

DAILY_TRAN_DETAIL_TABLE_idx_1.sql /* Index 1 creation for DTD */

DAILY_TRAN_DETAIL_TABLE_idx_2.sql /* Index 2 creation for DTD */

DAILY_TRAN_DETAIL_TABLE_idx_3.sql /* Index 3 creation for DTD */

DAILY_TRAN_DETAIL_TABLE_idx_4.sql /* Index 4 creation for DTD */

DAILY_TRAN_DETAIL_TABLE_idx_5.sql /* Index 5 creation for DTD */

DAILY_TRAN_DETAIL_TABLE_idx_6.sql /* Index 6 creation for DTD */

DAILY_TRAN_DETAIL_TABLE_idx_rename.dat /* has value 6 inside this dat file */

DAILY_TRAN_DETAIL_TABLE_trg_rename.dat /* has value 0 inside */

4.2 DTD Purge: Step 2

As part of the second step set of SQL and dat files for DTH will be generated

bash->ls *.sql *.dat

DAILY_TRAN_HEADER_TABLE.sql /* create table for DTH */

DAILY_TRAN_HEADER_TABLE_idx_rename.sql /* rename DTH to ETH */

DAILY_TRAN_HEADER_TABLE_idx_1.sql /*Index 1 for DTH */

DAILY_TRAN_HEADER_TABLE_idx_2.sql /*Index 2 for DTH */

DAILY_TRAN_HEADER_TABLE_idx_rename.dat /* has value 2 inside this dat file */

DAILY_TRAN_HEADER_TABLE_trg_rename.dat /* has value 0 inside */

Finacle Application End of Day Page 22 of 42 Author : Kittichok Chaisaksriskul

and Begin of Day Process Copyright © YIP IN TSOI & CO., LTD. Created Date : July 29, 2014

COMMERCIAL-IN-CONFIDENCE
 4.3 DTD Purge: Step 3

Dynamically the sql to CTD view drop is created and run with EST table status updated.

CTD_view_drop.sql

EST STATUS

View CTD dropped.

4.4 DTD Purge: Step 4

Dynamically the sql to CTH view drop is created and run with EST table status updated.

CTH_view_drop.sql

EST STATUS

View CTH dropped.

4.5 DTD Purge: Step 5

Dynamically the sql to ETD table drop is created and run with EST table status updated.

EOD_TRAN_DETAIL_TABLE_tbl_drop.sql

EST STATUS

Table ETD dropped.

4.6 DTD Purge: Step 6

Dynamically the sql to ETH table drop is created and run with EST table status updated.

EOD_TRAN_HEADER_TABLE_tbl_drop.sql

EST STATUS

Table ETH dropped.

Finacle Application End of Day Page 23 of 42 Author : Kittichok Chaisaksriskul

and Begin of Day Process Copyright © YIP IN TSOI & CO., LTD. Created Date : July 29, 2014

COMMERCIAL-IN-CONFIDENCE
 4.7 DTD Purge: Step 7

Dynamically the sql to DTD table rename to ETD is created and run with EST table
status updated.

DETAIL_tbl_rename.sql

EST STATUS

Table DTD renamed to ETD

4.8 DTD Purge: Step 8

Dynamically the sql to DTH table rename to ETH is created and run with EST table
status updated.

HEADER_tbl_rename.sql

EST STATUS

Table DTH renamed to ETH

4.9 DTD Purge: Step 9

Runs the SQL DAILY_TRAN_DETAIL_TABLE_idx_rename.sql created in Step 1

EST STATUS

INDEX renamed on ETD.

4.10 DTD Purge: Step 10

Runs the SQL DAILY_TRAN_ HEADER_TABLE_idx_rename.sql created in Step 1

EST STATUS

INDEX renamed on ETH.

Finacle Application End of Day Page 24 of 42 Author : Kittichok Chaisaksriskul

and Begin of Day Process Copyright © YIP IN TSOI & CO., LTD. Created Date : July 29, 2014

COMMERCIAL-IN-CONFIDENCE
 4.11 DTD Purge: Step 11

Dynamically the sql to CTD table create is created from $TBA_VIEWS/CTD.sql and run
with EST table status updated.

CTD_view_cre.sql

EST STATUS

View CTD created.

4.12 DTD Purge: Step 12

Dynamically the sql to CTH table create is created from $TBA_VIEWS/CTH.sql and run
with EST table status updated.

CTH_view_cre.sql

EST STATUS

View CTH created.

4.13 DTD Purge: Step 13

Runs the SQL DAILY_TRAN_DETAIL_TABLE.sql created in Step 1

EST STATUS

Table DTD created.

Finacle Application End of Day Page 25 of 42 Author : Kittichok Chaisaksriskul

and Begin of Day Process Copyright © YIP IN TSOI & CO., LTD. Created Date : July 29, 2014

COMMERCIAL-IN-CONFIDENCE
 4.14 DTD Purge: Step 14
Check the DAILY_TRAN_DETAIL_TABLE_idx_rename.dat created in Step 1 and run the
sql’s and update EST table

DAILY_TRAN_DETAIL_TABLE_idx_1.sql

DAILY_TRAN_DETAIL_TABLE_idx_2.sql

DAILY_TRAN_DETAIL_TABLE_idx_3.sql

DAILY_TRAN_DETAIL_TABLE_idx_4.sql

DAILY_TRAN_DETAIL_TABLE_idx_5.sql

DAILY_TRAN_DETAIL_TABLE_idx_6.sql

EST STATUS

Indexes created on DTD.

4.15 DTD Purge: Step 15

Check the DAILY_TRAN_DETAIL_TABLE_trg_rename.dat created in Step 1 and since it’s
always 0 do nothing but update status in EST.

EST STATUS

Triggers created on DTD.

4.16 DTD Purge: Step 16

Runs the SQL DAILY_TRAN_ HEADER_TABLE.sql created in Step 1

EST STATUS

Table DTH created.

Finacle Application End of Day Page 26 of 42 Author : Kittichok Chaisaksriskul

and Begin of Day Process Copyright © YIP IN TSOI & CO., LTD. Created Date : July 29, 2014

COMMERCIAL-IN-CONFIDENCE
 4.17 DTD Purge: Step 17

Check the DAILY_TRAN_HEADER_TABLE_idx_rename.dat created in Step 1 and run the

sql’s and update EST table.

DAILY_TRAN_ HEADER_TABLE_idx_1.sql

DAILY_TRAN_ HEADER_TABLE_idx_2.sql

EST STATUS

Indexes created on DTH.

4.18 DTD Purge: Step 18

Check the DAILY_TRAN_HEADER_TABLE_trg_rename.dat created in Step 1 and since

it’s always 0 do nothing but update status in EST.

EST STATUS

Triggers created on DTH.

4.19 DTD Purge: Step 19

Creates the ACLI, DTD_ACID and DTH_CTH views based on the $TBA_VIEWS sql files
and run them.

ACLI_cre.sql

DTD_ACID_cre.sql

DTH_CTH_cre.sql

EST STATUS

VIEWS created on CTD and CTH.

Finacle Application End of Day Page 27 of 42 Author : Kittichok Chaisaksriskul

and Begin of Day Process Copyright © YIP IN TSOI & CO., LTD. Created Date : July 29, 2014

COMMERCIAL-IN-CONFIDENCE
 4.20 DTD Purge: Step 20
Reads the .dat files created to know the count of the index and trigger sql files created
so that it can delete the sql’s in the below step.

DAILY_TRAN_DETAIL_TABLE_idx_rename.dat

DAILY_TRAN_HEADER_TABLE_idx_rename.dat

DAILY_TRAN_DETAIL_TABLE_trg_rename.dat

DAILY_TRAN_HEADER_TABLE_trg_rename.dat

Delete the below SQL created in earlier steps

CTH_view_drop.sql

CTD_view_drop.sql

CTH_view_cre.sql

CTD_view_cre.sql

DETAIL_tbl_rename.sql

HEADER_tbl_rename.sql

DAILY_TRAN_DETAIL_TABLE.sql

DAILY_TRAN_HEADER_TABLE.sql

DAILY_TRAN_DETAIL_TABLE_idx_rename.sql

DAILY_TRAN_HEADER_TABLE_idx_rename.sql

DAILY_TRAN_DETAIL_TABLE_idx_1.sql

DAILY_TRAN_DETAIL_TABLE_idx_2.sql

DAILY_TRAN_DETAIL_TABLE_idx_3.sql

DAILY_TRAN_DETAIL_TABLE_idx_4.sql

DAILY_TRAN_DETAIL_TABLE_idx_5.sql

DAILY_TRAN_DETAIL_TABLE_idx_6.sql

DAILY_TRAN_HEADER_TABLE_idx_1.sql

Finacle Application End of Day Page 28 of 42 Author : Kittichok Chaisaksriskul

and Begin of Day Process Copyright © YIP IN TSOI & CO., LTD. Created Date : July 29, 2014

COMMERCIAL-IN-CONFIDENCE
 DAILY_TRAN_HEADER_TABLE_idx_2.sql

DAILY_TRAN_HEADER_TABLE_idx_rename.dat

DAILY_TRAN_HEADER_TABLE_trg_rename.dat

DAILY_TRAN_DETAIL_TABLE_idx_rename.dat

DAILY_TRAN_DETAIL_TABLE_trg_rename.dat

EOD_TRAN_HEADER_TABLE_tbl_drop.sql

EOD_TRAN_DETAIL_TABLE_tbl_drop.sql

ACLI_cre.sql

DTD_ACID_cre.sql

DTH_CTH_cre.sql

4.21 DTD Purge: Step 21

Call the DTDPurge.com. this always return success. Execute ETD_TO_HTD.sql after
finding the PATH for the same.

5. FTD Purge

DB_STAT_CODE DB_INIT_STAT_CODE

K 4

/* K – indicates CENTRALBODSTARTED */
/* 4 – indicates CALLCBODFTDPURGE */

It displays the message “AUS BOD Future table movement in progress...”

Finacle Application End of Day Page 29 of 42 Author : Kittichok Chaisaksriskul

and Begin of Day Process Copyright © YIP IN TSOI & CO., LTD. Created Date : July 29, 2014

COMMERCIAL-IN-CONFIDENCE
 6. Start CBOD script

DB_STAT_CODE DB_INIT_STAT_CODE

K 100

/* K – indicates CENTRALBODSTARTED */
/* 100 – indicates STARTCBODSCRIPT */

7. Batch for Reversal of Reval Transactions

DB_STAT_CODE DB_INIT_STAT_CODE

K 101

Reval Transactions: Valuation of foreign currencies pegged to the local currency to

derive the notional profit or loss due to the fluctuation in the exchange rates is called
Revaluation. Usually banks revalue their foreign currency holdings every day. Reval
transactions is used for calculation of revaluation income or expense.

- Exe name: babx4490

8. FTX to GAM movement

DB_STAT_CODE DB_INIT_STAT_CODE

K 102

FTX to GAM movement: FTX stands for FUTURE_VALUE_DT_TRAN_TABLE.For future

value dated transactions, clear balance is not updated at the time of transaction creation but
on the future value date. For such transactions the basic requirement is to realize those
transactions on the future value date when the value date becomes the BOD date.This
program will process all the Future value dating transactions which are supposed to be
Finacle Application End of Day Page 30 of 42 Author : Kittichok Chaisaksriskul
and Begin of Day Process Copyright © YIP IN TSOI & CO., LTD. Created Date : July 29, 2014

COMMERCIAL-IN-CONFIDENCE
 effective on that date. It will logically delete those records from Future Value Dated
Transaction table (FTX) and update Clear Balance of the accounts; however it will not process
clearing transactions. During regularization phase of the clearing cycle, future value dated
clearing transactions will be effective.

- Exe name: Babx4489

9. Running user defined batch jobs

DB_STAT_CODE DB_INIT_STAT_CODE

K 103

- Exe name: Babx4009

10. K999

DB_STAT_CODE DB_INIT_STAT_CODE

K 999

11.Change Password

DB_STAT_CODE DB_INIT_STAT_CODE

K PWD

/* K – indicates CENTRALBODSTARTED */
/* PWD – indicates CHGPASSWDPRGM */

Finacle Application End of Day Page 31 of 42 Author : Kittichok Chaisaksriskul

and Begin of Day Process Copyright © YIP IN TSOI & CO., LTD. Created Date : July 29, 2014

COMMERCIAL-IN-CONFIDENCE
 12.Call BOD message to CSIS

DB_STAT_CODE DB_INIT_STAT_CODE

K 5

/* K – indicates CENTRALBODSTARTED */
/*5 – indicates CALL_BOD_MESGTOSIS */

Displays the meesage “BNY Starting BOD Finacle@Branch handover ...”

Call the exec_handovermon.com in background to do the job.

13.Last CBOD Job

DB_STAT_CODE DB_INIT_STAT_CODE

K ZZZ

/* K – indicates CENTRALBODSTARTED */
/* ZZZ – indicates LASTCBODJOB */

Error Messages:

The error messages or progress information can be checked from $TBA_TRACE_DIR

/log/[SOLID]_CBOD.log

The Messages are also sent to the Op Console with the service name CBOD_[solid]_PROGRESS.

Finacle Application End of Day Page 32 of 42 Author : Kittichok Chaisaksriskul

and Begin of Day Process Copyright © YIP IN TSOI & CO., LTD. Created Date : July 29, 2014

COMMERCIAL-IN-CONFIDENCE
 6. ISOLOP – Initiate Service Outlet Operations

Initiate Service Outlet Operations (ISOLOP) is a process run by the user at a SOL at the start of
each working day. No user is allowed to start transactions, financial or non-financial, before ISOLOP is
done. All batch jobs specific to a SOL must run during this process.

This process cannot be invoked when SAF replay of transactions related to Connect24 are in
progress. An error "SAF replay in progress" is displayed. The user can proceed further only after the SAF
replay is complete.

Pre-requisites:

Central BOD of the datacenter must be over.

STEPS AND PROCESS:

Step Description Exe name

600 User defined batch jobs Babx4009

601 Enhancing TOD limits for accounts Babx4014

602 Executing standing instructions Sibx4003

603 Site specific scripts execution Isolop.site

JJJ LastScript Job , isolop completed.

Error Messages:

The error messages or progress information can be checked

from $TBA_TRACE_DIR/log/[SOLID]_ISOLOP.log

If the variable TBA_TRACE_DIR is not set, the logs are put in the $HOME directory of the user who is
running the process.

The Messages are also sent to the Op Console with the service name ISOLOP_[solid]_PROGRESS.

After ISOLOP is successfully completed, the DB_STAT_CODE would change to C.

Finacle Application End of Day Page 33 of 42 Author : Kittichok Chaisaksriskul

and Begin of Day Process Copyright © YIP IN TSOI & CO., LTD. Created Date : July 29, 2014

COMMERCIAL-IN-CONFIDENCE
 7. Other related processes

7.1 Reinitiating transfer of history transactions – METOH

As a part of the Begin of Day process, transactions records are moved from the daily
transaction table to the history Transaction table.

The movement process works as follows:

1) Drop CTD and CTH views

2) Drop ETD and ETH tables

3) Rename DTD to ETD and DTH to ETH

4) Recreate view CTD and CTH

4) Recreate DTD and DTH tables

5) Recreate indexes on DTD and DTH tables

6) Initiate transfer of records from ETD to HTD and ETH to HTH in background

Finacle Application End of Day Page 34 of 42 Author : Kittichok Chaisaksriskul

and Begin of Day Process Copyright © YIP IN TSOI & CO., LTD. Created Date : July 29, 2014

COMMERCIAL-IN-CONFIDENCE
 The movement will be initiated in background and control will come to the program
immediately so that end of day operations can continue. The movement is sol parallelized. To check
the return status of the process, a script “ETDtoHTDFailureCapture.scr” has been provided. This script
internally calls a com script “ETDToHTDUserDefined.com” which can be used for customized action on
return of movement process. By default, this com script calls “mail” command to send mail to
concerned persons.

The menu option METOH has also been provided to reinitiate this transfer in case it fails due
to any reason. The menu option does not take any user input and processes for all the sol ids. This
menu needs to be invoked only if the process of moving the history transaction during the Begin of
Day is not completed.

7.2 Verify previous day’s transactions – PTV

Using the above menu, user can verify transactions of the previous period since TV will
list only transactions of the current day.

Finacle Application End of Day Page 35 of 42 Author : Kittichok Chaisaksriskul

and Begin of Day Process Copyright © YIP IN TSOI & CO., LTD. Created Date : July 29, 2014

COMMERCIAL-IN-CONFIDENCE
 7.3 Changing User’s Context SOL – HCCS

During the End-of-day operations, sometimes it is required for the system operator to
switch SOLs to clear some transaction records. Using the menu option HCCS, user can change
to another SOL temporarily and work as if he/she is a user of that particular SOL.

This menu can be invoked only if the user tenor is Free at UPM.

Also and script event has been provided to customize this menu to restrict user’s from
changing SOL depending upon various requirements. The script name is
HasBranchEODBODEnded.scr

8. Related tables

TABLE ABBR TABLE NAME

GCT SOL_GROUP_CONTROL_TABLE
SOL SERVICE_OUTLET_TABLE
BJS BATCH_JOB_SCHEDULER_TABLE
EST EOD_STATUS_TABLE
UPR USER_PROFILE_TABLE
LGI LOGIN_TABLE
LGT LOGIN_LOG_TABLE

Finacle Application End of Day Page 36 of 42 Author : Kittichok Chaisaksriskul

and Begin of Day Process Copyright © YIP IN TSOI & CO., LTD. Created Date : July 29, 2014

COMMERCIAL-IN-CONFIDENCE
 9. Related menu options

MENU OPTION DESCRIPTION

ABH Initiate After Business Hours Process
BGJQM Background Job Queue Maintenance
BJE Batch Job Executioner
BJSINQ Query on BJS table
BJSTI BJS Table Inquiry
HBJSTM BJS Table Maintenance
CBOD Initiate BOD Central Process
HCCS Change Context Service Outlet
HCCST Close Cash Transactions
CEOD Initiate EOD Central Process
CSOLOP Initiate SOL EOD Process
HCXFT Close Transfer Transactions
HDTE Delete Transaction In Entered Status
ISOLOP Initiate Service Outlet BOD Process
METOH Transaction record movement
HOCST Open Cash Transactions
HOXFT Open Transfer Transactions
HPPT Proxy Post Transaction In Entered Status
PTV Previous Day Transaction Verification
HRIST Reconcile Inter Service Outlet transactions
SOLSTAT Check status of all the SOLs
SOLVAL Validations on a SOL before initiating the EOD/BOD related
jobs

10. Key points to be noted

1. There should not be any duplicate sessions while the EODBOD process is carried out.
2. If any of the process fails at a particular step, the user should check out the fatal logs and
correct the error in fatal first .After that he should log out and re run that step after updating
appropriate flags in SOL, EST table.

Finacle Application End of Day Page 37 of 42 Author : Kittichok Chaisaksriskul

and Begin of Day Process Copyright © YIP IN TSOI & CO., LTD. Created Date : July 29, 2014

COMMERCIAL-IN-CONFIDENCE
 3. In case any lock is created on any table, please use the below queries to find out the locked
table
a. select oracle_username, os_user_name, session_id, process, object_name from
v$locked_object a, dba_objects b where a.object_id = b.object_id and
oracle_username='TBAGEN' and object_name in
('DAILY_TRAN_DETAIL_TABLE','DAILY_TRAN_HEADER_TABLE') order by
process
b. select * from v$locked_object where object_id in (select object_id from dba_objects
where object_name = 'DAILY_TRAN_DETAIL_TABLE');
c. select * from dba_dml_locks where name = 'DAILY_TRAN_DETAIL_TABLE';
4. If any core is getting formed, share the pstack of the core.
5. Make sure that un-posted transactions are not present before running CBOD, If EOD throws
any fatal, make sure that the error/issue is fixed & then only proceed to run CBOD.
6. Try to post unposted transactions using PPT menu only. Avoid manual DB update as much as
possible.
7. Always check the Date & confirm before proceeding to run any process.
8. If suppose CBOD fails at K2, then the error has to be resolved first and after that update the
db_int_stat_code to K1 and re run the CBOD again.
9. Do not update the status field in EST table without proper analysis of the situation and the
error. If updated wrongly entire data in DTD and DTH could be lost.
10. Do not do any update to next execution date (next_exec_date in BJS table) of any batch job
when batch job executioner is running.
11. Never restart CBOD without updating db_int_stat_code to a correct value. Otherwise the
db_stat_date will be incremented again.
12. Never skip EAB/GST rebuild.

Finacle Application End of Day Page 38 of 42 Author : Kittichok Chaisaksriskul

and Begin of Day Process Copyright © YIP IN TSOI & CO., LTD. Created Date : July 29, 2014

COMMERCIAL-IN-CONFIDENCE
 11. Some common issues faced during EOD/BOD and there
resolutions.

1. On running any menu of EOD/BOD sometimes we get no logs in the back end. The status doesn’t
change and the failure report is also zero sized. Here generally the problem is with the next execution
date of the batch job that’s tagged for that menu. Just check the next execution date and then re-
execute the batch job.
2. Also EOD/BOD is stuck sometimes due to space issue in user’s partition. We execute EOD or BOD
process and we find that no logs are getting generated. This could be because of space issue. Before
starting EOD/BOD, we need to check that we have enough space in user’s partition.
3. Also sometimes the EOD/BOD processes fail due to several batch programs running in back end in
some other user id. These batches we come to know from the failure report in the logs as a list and
the user id in which it is running. Post this we can use menu HSAC to delete the batch jobs and then
retry running the process.
4. In case of any deadlock issue encountered, please analyse the below mentioned logs.
a. In order to find the which entity got locked during the deadlock, we need the below things:
i. Database Alert Log
Oracle will write the alert.log file to the directory as specified by the
BACKGROUND_DUMP_DEST parameter. If this parameter is not set, the alert.log will
be created in the ORACLE_HOME/rdbms/trace directory. In case of a deadlock Oracle
records the following line in the alert log:

ORA-00060: Deadlock detected. More info in file <<path>>/<tracefilename>>.trc.

ii. Trace File

Note down the trace file path and name in the above step. This file will be available in
the USER_DUMP_DEST directory.With this trace file we would be able to find more
information on the deadlock. It will tell us the sessions that were contending for the
lock, the query that caused the deadlock etc.

Finacle Application End of Day Page 39 of 42 Author : Kittichok Chaisaksriskul

and Begin of Day Process Copyright © YIP IN TSOI & CO., LTD. Created Date : July 29, 2014

COMMERCIAL-IN-CONFIDENCE
 5. Identifying Locking Issues
In Finacle if locks are observed in the database, the locked sessions might go in to infinite waiting
mode and online operations might get affected.

In case of a locking contention, the resource will get freed under the following circumstances:

1. The lock HOLDER session issues a commit or rollback

2. The lock HOLDER session is killed explicitly.

This section lists the steps involved in identifying and troubleshooting locking issues.

a. Try to find out the blocking sessions in the database.

SELECT/*+RULE */ DECODE(a.request, 0,'HOLDER','WAITER'), a.sid , b.process, a.lmode,

b.TYPE, a.ctime,substr(b.program,1,17),b.event

FROM gv$lock a,gv$session b

WHERE a.sid=b.sid and

(a.id1, a.id2, a.TYPE ) IN (SELECT c.id1, c.id2, c.TYPE FROM v$lock c WHERE c.request>0)

ORDER BY a.id1, a.request;

Note: In case of a RAC setup, we use gv$ instead of v$ views. Also instance ID can be
included as part of the WHERE clause.

b. Find out which row is locked.

select sid,row_wait_file#,row_wait_block#,row_wait_row#       
from gv$session
where sid =’&blocking_session’;

select object_type,owner,object_name
from dba_objects
where object_id=<row_wait_obj#>;

Finacle Application End of Day Page 40 of 42 Author : Kittichok Chaisaksriskul

and Begin of Day Process Copyright © YIP IN TSOI & CO., LTD. Created Date : July 29, 2014

COMMERCIAL-IN-CONFIDENCE
 Use the values obtained in the previous two queries to get the row that is locked:

select <column_names>
from <owner>.<object_name>
where rowid = dbms_rowid.rowid_create(1, <row_wait_obj#>, <row_wait_file#>,
<row_wait_block#>, <row_wait_row#>);

c. Get details on the blocking process for further analysis

select username, status, machine, program, process, client_info from gv$session

where sid= <blocking_session>;

From the operating system level, it would be helpful to have the process trace. In AIX the
output of the following commands will help in issue analysis: (The PID will the process column
obtained from the previous query)

proctree <PID>
procstack <PID>

After taking the data for analysis, you may kill the blocking process:

Alter system kill session (<SID>,<SERIAL#>);

12. Flashback

As a part of daily operations there are certain operations that need to be carried out during the
beginning of day and End of Day. These are termed as EOD/BOD operations.

The EOD processes are executed as under:

Finacle Application End of Day Page 41 of 42 Author : Kittichok Chaisaksriskul

and Begin of Day Process Copyright © YIP IN TSOI & CO., LTD. Created Date : July 29, 2014

COMMERCIAL-IN-CONFIDENCE
 ABH – After business hours

CSOLOP – Service out let end of day

CEOD – Central end of day

CBOD – Central beginning of day

ISOLOP – Service out let beginning of day

ABH is a not a mandatory option. CSOLOP will complete ABH before proceeding.

Batch jobs can be set, which can be executed during each of these operations. Batch jobs are
setup through HBJSTM menu option.

Exceptions can be set up in the HSCFM and GSPM menu options to warn the user about
incomplete processes before initiating the End of day operations.

Finacle Application End of Day Page 42 of 42 Author : Kittichok Chaisaksriskul

and Begin of Day Process Copyright © YIP IN TSOI & CO., LTD. Created Date : July 29, 2014

COMMERCIAL-IN-CONFIDENCE