FINACLE EOD & BOD

Introduction

• End-of-day & begin-of-day are operations performed in Finacle to mark the

logical end-of-day and mark the beginning of next working day.

• The entire EOD/BOD Process can be either initiated from the Branches or
from the data centre depending on the Bank’s requirement.
 Features of 24 x 7 EOD
• End of day processing and business date change are decoupled.
• Batch job processing is enhanced to reduce the dependency on end of day
events and enable automatic execution from an external scheduler
• Eliminating CSIS completely from a normal operational perspective.
• Using LSIS only for Network fall back
• Using CSIS only for planned downtimes.
• DC can change the date without any dependency on SOL and vice versa
• DC cannot be closed for 2-1-2006 until all the sols are closed for 2-1-2006
• Date difference between SOL and DC cannot be greater than 1
 Configuring parameters to enable the
24 x 7 process of day change

• IMPLEMENTED_24X7_FLG = Y in GCT table.

• IS24X7IMPLEMENTED = Y in application.properties file
24 x 7 - Sol level end of day processing
 24 x 7 - Sol level end of day processing

Date movement for SOL from 29-10-2020 to 30-10-2020

Events db_stat_code sol_cls_flg sol_cls_date sol_bod_date

Beginning Y Y 28-10-2020 29-10-2020

HISCOD I Y 28-10-2020 29-10-2020

PRESCOD P Y 28-10-2020 29-10-2020

HSCOD M N 29-10-2020 30-10-2020

POSTCOD N N 29-10-2020 30-10-2020

HSOLCOP B N 29-10-2020 30-10-2020

HSCOLD Y Y 29-10-2020 30-10-2020

 Date difference between sol operating date and that of data center cannot be > 1
24 x 7 - Data center level end of day processing
 24 x 7 - Data center level end of day processing

Date movement for DC from 14-09-2007 to 15-09-2007

Events dc_stat_code dc_cls_flg dc_cls_date dc_stat_date

Beginning Y Y 28-10-2020 29-10-2020

PREBKOD P Y 28-10-2020 29-10-2020

HBKOD M N 29-10-2020 30-10-2020

POSTBKOD N N 29-10-2020 30-10-2020

HBKCOP B N 29-10-2020 30-10-2020

HBKOLD Y Y 29-10-2020 30-10-2020

Creation of Job Group Codes
• Menu Option : HRRCDM

• Sol Level Events

• Pre SCOD
• Post SCOD
• SOLCOP
• Post SCOLD
• Bank level Events
• Pre BKCOD
• Post BKCOD
• BKCOP
• Post BKCOLD
 Job Group Event Maintenance
• Menu HJEM : Linked to Respective Day End process.

• Job group – Event is a one-to-one relationship i.e, only one job group can
be linked to one event and vice versa.
 Jobs for SOL Level
• The batch job babx4548 / 1 (BSOLSTATUPD / 1) is set for each status change at
various events of the day change process.
• PRSL1 (change the db_stat_code for the sol from Y to I, next_exec_date = 2-
Jan-06)
• PRSL2 (Change the db_stat_code for the sol from I to P, next_exec_date = 2-
Jan-06)
• PSSCD (PSSCD – Change the db_stat_code for the sol from M to N,
next_exec_date = 3-Jan-06)
• SLCOP (Change the db_stat_code for the sol from N to B, next_exec_date = 2-
Jan-06)
• The above SOL level batch jobs need to be replicated to all the SOLs in the
application.
• The above explained 4 sol level date change batch jobs should have the
holiday frequency set as E – Execute on a holiday only. The other batch jobs
set in the same events can have the holiday frequency as per bank's
requirements.
 Jobs for Bank Level
• The batch job babx4548 / 1 (BSOLSTATUPD / 1) is set for each status change at
various events of the day change process.
• PRBK1 – change the dc_stat_code for the DC from Y to I, next_exec_date = 2-
Jan-06
• PRBK2 – Change the dc_stat_code for the sol from I to P, next_exec_date = 2-
Jan-06
• PSBKD – Change the dc_stat_code for the sol from M to N, next_exec_date =
3-Jan-06
• BKCOP – Change the dc_stat_code for the sol from N to B, next_exec_date =
2-Jan-06

• The above Bank level batch jobs can be set from any sol. These are not to be
replicated. Onetime setup from any SOL is sufficient.
 Validation Maintenance

• Menu : HSVAM
• Validation Events
• SOL date change
• DC date change
• SOL closure
• DC closure
 Validation Type
 System Validations
 Bank Defined Validations
 Custom Validations
 Initiate SOL Change of Date Process
• HISCOD – Initiate SOL change of date

• This is an optional step. This can be ignored since the initiation is also
taken care as part of next process.
• All the logged in users get the flash message notifying them of the
impending date change process.
• At the end of this process db_stat_code changes from Y to I.
• sol_cls_flg value will be Y
 SOL Date Change Process
• Menu: HSCOD – SOL change of operating date
• The operating date of SOL can be changed from 2-Jan-2007 to 3-Jan-2007 only if
the Bank is closed for 1-Jan-2007
• To run the menu, the db_stat_code should be either I or Y
• Pre Scod – Pre date Change event
• This step includes the batch jobs that need to be run
before the date change for the set
• PRSL1 will be first job to be run in this event indicating the
beginning of the process.
• PRSL2 will be last job to be run in this event indicating the
completion of the process.
• All the batch jobs will be run as of 2-Jan-2006 i.e the
current operating date
• db_stat_code will be P and sol_cls_flg will be Y
 SOL Date Change Process
• SCOD
• This is the event at which the sol date actually changes.
• Validates for any holiday set between current BOD and next working
date.
• Runs any site specific script set by the user.
• Runs the babx4498 process, validation batch job which executes all
the system, bank definedand custom validations set at the SVAM level.
• The SOL date changes after the successful completion of the above
processes
• If any of the blocking type of validation fails, then the sol_cls_flg will
be updated to F and the process is halted.
• Just before updating the date for the sol, all the online users are
sacked by the system and the transaction sequence is generated for
the new working date
• The logged in users will be thrown the below error and the core
session is terminated
• db_stat_code changed to M and sol_cls_flg will be N
 SOL Date Change Process
• Post Scod – Post Date change event
• This step includes the batch jobs that need to be run immediately
after the date change for the set / sol.
• In case of failure of any blocking job in this event, the process is
halted. After the necessary changes are done, HSCOD is fired again
with ‘Run only post date change jobs’ flag checked.
• The last job to get executed in this event is PSSCD
• An option has been provided in the babx4548 batch job to bypass
SOLCOP.
• This is set by specifying the bypass option in the parameter field of
PSSCD job.
• If ByPass is set as N, then db_stat_code=N and col_cls_flg=N
• If ByPass is set as Y, then db_stat_code=B and col_cls_flg=N
 SOL CLOSURE OPERATIONS
• Menu : HSOLCOP
• This process is invoked if the bypass option was No in the earlier
step
• Before starting SOLCOP, the db_stat_code should be N (HSCOD
completed successfully)
• Inputs in the screen are set ID and No. of parallel Sols.
• This menu executes all the batch jobs with job group linked to
this event, as of yesterday.
• In case of transaction creating batch jobs, transaction date will
be the previous working date i.e. 2-Jan-2006 but posting will be
based on real time balance.
• In case of reporting batch jobs, data fetching and printing will be
based on previous working date i.e. 2-Jan-2006.
• SLCOP will be last batch job to get executed in this event.
• db_stat_code will be ‘B’ and sol_cls_flg=‘N’ after the end of this
process
 SOL CLOSURE OF LAST DAY

• Menu : HSCOLD
• Before starting SCOLD, the db_stat_code should be B.(HSOLCOP
completed successfully)
• Inputs in the screen are set ID, No. of Parallel Sols and Run post
SCOLD jobs flag.
• This menu does the basic validation based on db_stat_code and Bank
status
• Fires the validation batch job babx4498 – HSVAM validations for sol
closure event
• Updates the sol to closed status
• Fires the batch jobs set for execution after closure of last day
• If any blocking validation fails, the sol_cls_flg is updated to F and the
closure stops
• Restart option has been provided to rerun the jobs in case any
blocking type of batch job fails, as “Run post scold jobs” flag in the
menu screen.
• db_stat_code = ‘Y’ and sol_cls_flg=‘Y’ after the end of this process
• This process completes the end of Day Processing @ SOL Level
 SOL Status
• Menu : HSSI
• Throughout the SOL level date change and end of day operations, the
status of each sol can be inquired through this menu
 BANK Level Date Change and EOD processing
• DC_STAT_CODE = ‘Y’ and DC_CLS_FLG = ‘Y’ in GCT.
• There is no dependency on SOL dates for the DC date to change i.e the
data center date can be either ahead or behind that of a SOL.
• Date difference between SOL and DC cannot be greater than 1
 BANK CHANGE OF DATE
• Menu Option : HBKOD
• To run the menu, the dc_stat_code should be Y
• Input in the screen is run only post cod flag
• The BKOD process involves 3 events, namely
• Pre Bank Change of Date
• Actual Change of Date
• Post Change of Date
 Pre Bank Change of Date
• This step includes the batch jobs that need to be run before the date
change for the Bank.
• PRBK1 will be first job to be run in this event. This indicates the process
initiation.
• dc_stat_code = ‘I’ and dc_cls_flg=‘Y’
• PRBK2 will be last job to be run in this event and will mark the successful
completion of predate change event.
• All the batch jobs will be run as of 2-Jan-2006 i.e. Current working date
• dc_stat_code will become P and dc_cls_flg will be N after this process.
 Bank Change of Date
• This is the event at which the Bank date actually changes.
• Before the actual date change, the system
• Validates for any holiday set between current BOD and next
working date
• Runs any site specific script set by the user
• Does the License check (mandatory)
• Executes the Fincron posting
• Executes the Inter SOL reconciliation (RIST)
• Runs the babx4498 process, validation batch job which executes
all the system, bankdefined and custom validations set at the
SVAM level for the DC date change .
 The Bank date changes after the successful completion of the above
processes.
 Process is stopped if the License check fails
 If any of the blocking type of validation fails, then the dc_cls_flg will
be updated to F and the process is halted.
 dc_stat_code will be M and dc_cls_flg will be N
 Post Bank Date Change Event
• This step includes the batch jobs that need to be run
immediately after the date change of the data center.
• In case of failure of any blocking job in this event, the
process is halted. After the necessary changes are done,
HBKOD is again run with ‘Run post BKOD jobs’ flag
checked.
• The last job to get executed in this event is PSBKD.
• An option has been provided in the babx4548 batch job to
bypass BKCOP
• If ByPass flag is set as Y then dc_stat_code will be B and
dc_cls_flg=‘Y’..
• If ByPass flag is set as N then dc_stat_code will be N and
dc_cls_flg =‘Y’ then bank HBKCOP (Bank Closure) will be
Mandatory
 Bank Closure Operation
• Menu : HBKCOP
• This process is invoked if the bypass option was No in the earlier step
• Before starting HBKCOP, the dc_stat_code should be N (HBKOD
successfully completed)
• This menu executes all the batch jobs with job group linked to this
event, as of yesterday
• In case of transaction creating batch jobs, transaction date will be the
previous working date i.e.2-Jan-2006 but posting will be based on real
time balance
• In case of reporting batch jobs, data fetching and printing will be
based on previous working date i.e. 2-Jan-2006
• BKCOP will be the Last Batch Job to get executed in this operation
• dc_stat_code will be B and dc_cls_flg= Y after this
 Bank Closure of Last Date
• Menu HBKOLD
• Before starting BKOLD, dc_stat_code should be B and dc_cls_flg should be N / F.
• Data center can be closed for the last day only if all the SOLs are closed for the last day
• Input in the screen is Run post BKOLD jobs flag.
• Following are the validations done :
• Basic validations based on dc_stat_code and SOL status
• Fincron posting
• Forced posting
• Inter-SOL reconciliation
• Update dc_stat_code to X
• EAB-GST build
• ETD/ETH to HTD/HTH movement (if record exists in ETD/ETH)
• DTD/DTH to HTD/HTH movement
• Dropping and recreation of Transaction, CAMT and PST sequences
• Update dc_stat_code to Y and dc_cls_flg to Y
• Fires the batch job set up for execution after DC closure event
 Bank Closure of Last Date
 If any of the validation fails, then the dc_cls_flg will be updated to F and
the process is halted.
 When HBKCOLD is fired:
 If dc_cls_flg = N/F and dc_stat_code = B, then steps 1 to 12 will
be followed
 If dc_cls_flg = Y and dc_stat_code = X, then steps 6 to 12 will be
followed
 If ‘Run only BKOLD jobs’ is checked, then step 12 will be executed
only provided dc_cls_flag = Y and dc_stat_code = Y
 db_stat_code will be Y and dc_cls_flg=Y
 This confirms the succesful completion of End of the Day
 Bank Status Inquiry
• Menu Option : HBSI
• Throughout the Bank level date change and end of day operations,
the status of the data center can be inquired through this menu
 SOL Cutoff Maintenance
• Menu HSCOFF
• This menu is used to mark / unmark a SOL in a SET as cutoff
• When the SOL is marked as cutoff, the db_stat_code is updated to Z
• When a sol is marked as cutoff
• If HSCOD is fired at the SET level, the SOL is excluded from the
process
• If HSOLCOP is fired at the SET level, the SOL is excluded from the
process
• If HSCOLD is fired at the SET level, the SOL is excluded from the
process
• Though a SOL can be segregated from the SET level day change
processes, these processes need to be run for the SOL to get it in sync
with the rest of the SOLs
 BATCH JOBS

• Batch Jobs can be defined using interface HBJSTM.

• Invoking can be done at
• SOL LEVEL
• BANK LEVEL
• Job Group can be defined using HRRCDM
• Job Group can be liked to the following events using HJEM
• PRESCOD (Pre SOL Change of Date)
• POSTSCOD(Post SOL Change of Date)
• POSTBKOD(Post DC Change of Date)
• PREBKOD( Pre DC Change of Date)
 BATCH JOBS CONTINUED

• SOLCOP ( SOL Close of Operations)

• BKCOP (Bank Close of Operations)
• POSTBKOLD ( Post Bank Close of Operations)
• POSTSCOLD (Post Sol Close of Operations)
• GEN (General – for User Execution)

•
 BATCH JOBS CONTINUED
• Jobs which can be executed as of last working day can be defined using HPDBJM (HPDBJINQ – for Inquiry &
HPDBJDEL for Deletion)
• Batch Job execution can be interfaced with external schedulers like Tivoli Work Load Scheduler.
• Batch Jobs can be Blocking or Non – Blocking or Independent.
• Frequency for the Batch Job can be defined.
• Batch Jobs can be run on previous date, next date or skipped.
 Other Menu Options

• SOL Cut-Off (HSCOFF) (to cut off a SOL from a particular set for
EOD Operations)
• HMOGM (Creating a Menu group)
• HMOSM ( Enabling and disabling Menu options during Date
Change based on user Work Class and Role ID)
QUESTIONS
THANKS FOR PARTICIPATING